Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Wrong clinical date

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

10 Posts

5 Users

0 Reactions

95 Views

RSS

rfisher

(@rfisher)

Posts: 126

Estimable Member

Topic starter

Any advice on how to handle a situation when a provider doesn't start a note on the same day as the visit and forgets to back date the clinical date?

Is adding an append with some dictation stating the visit took place on another date sufficient?

Anyone have a workflow or procedure to handle these situations?

Posted : May 19, 2015 8:33 am

acantu

(@acantu)

Posts: 722

Prominent Member

I usually have them send me the request to change it via SQL.

Just change the date and input the Unique SDID for the document.
You can change it using this script:::

UPDATE DOCUMENT SET CLINICALDATE = dbo.Convert_Date_to_ID('1/1/2015 10:00PM') WHERE SDID = 'INPUT SDID HERE'

Posted : May 19, 2015 8:41 am

SLHV

(@slhv)

Posts: 478

Honorable Member

We do it via SQL also. Ours is a little more detailed so I'll share it in case it's useful.I'd be interested to see how others resolve this as well.

Set @pid to the PID of the patient, @docid to the document ID in the chart, and @clinicaldate to the corrected clinical date.

When completed, ensure that you either commit to commit the change, or rollback to revert it (in case something went wrong).

declare @pid varchar (8), @docid varchar (4), @clinicaldate varchar (16);
set @pid = '82008';
set @docid = '177';
set @clinicaldate = '2011-09-23';
select document.pid, document.clinicaldate from document, patientprofile
where
document.pid = patientprofile.pid and
patientprofile.patientid = @pid and
document.visdocid = @docid;

begin tran
update document set document.clinicaldate = cast(DATEDIFF(second, '1960-01-01', @clinicaldate) as numeric) * '1000000' from document,patientprofile where document.pid = patientprofile.pid and patientprofile.patientid = @pid and document.visdocid = @docid;

select document.pid, document.clinicaldate from document, patientprofile where document.pid = patientprofile.pid and patientprofile.patientid = @pid and document.visdocid = @docid;

-- You MUST commit or rollback this transaction or you will bring the EMR to a screeching HALT!!!!!!!

--commit

--rollback

Posted : May 19, 2015 9:04 am

acantu

(@acantu)

Posts: 722

Prominent Member

The only issue with that SLHV is sometimes CPS will duplicate Vis Doc ID's. I have seen this for multiple offices.

Posted : May 19, 2015 9:57 am

dduschel

(@dduschel)

Posts: 207

Reputable Member

Can either of the above also be run on CEMR?

Posted : May 20, 2015 2:17 am

lkeith

(@lkeith)

Posts: 457

Honorable Member

Acantu - I don't want to just assume, but for your script, we would end that with Commit, correct? Also, can this be done if it is in either Signed or on hold status?

Thanks,

Linda

Posted : May 20, 2015 6:26 am

acantu

(@acantu)

Posts: 722

Prominent Member

Hi Dawn, yes, this can run on EMR Oracle, if you need assistance, please let me know.

Hi Linda, yes, it will work with both Signed and on Hold documents, also it should look like this, the original post was just the transaction script, but yes, should be embedded in a transaction, should be like this:

BEGIN TRY
BEGIN TRANSACTION

UPDATE DOCUMENT
SET CLINICALDATE = dbo.Convert_Date_to_ID('1/1/2015 10:00PM')
WHERE SDID = 'INPUT SDID HERE'

COMMIT

END TRY

BEGIN CATCH

IF @@ERROR > 0

ROLLBACK

END CATCH

Also, to get your SDID for your Document, you can run this script

SELECT SDID, SUMMARY, STATUS, dbo.Convert_ID_to_date(CLINICALDATE) AS CLINICALDATE, VISDOCID FROM DOCUMENT WHERE PID IN (SELECT PID FROM PatientProfile WHERE PatientId = 'ENTER PATIENT ID HERE' AND pstatus = 'A') AND VISDOCID = 'INPUT VISIT DOC ID HERE'

Posted : May 20, 2015 6:43 am

rfisher

(@rfisher)

Posts: 126

Estimable Member

Topic starter

What about the OBS values? They would still have the same date as when the original document was created.

Posted : May 20, 2015 7:44 am

acantu

(@acantu)

Posts: 722

Prominent Member

the OBS Values will stay the same, unless you want those to be changed, but usually we do not touch that as those are the dates that it was actually inputted.

Posted : May 20, 2015 7:46 am

dduschel

(@dduschel)

Posts: 207

Reputable Member

Thank you very much.

Posted : May 20, 2015 8:00 am

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed