MWL entry update

dumbterminal · Mar 3rd 2019

Hi!,

I am trying to test the MWL for updating an order from scheduled to completed using HL7 ORC tags. Have added ORC mappings in dicom.sql, the order.hl7 file and the same order with status updateorder.hl7 file. by loading the order file an entry is created into the worklist, by loading the updateorder file another entry is added. The concept im trying is that an order is sent via an HL7 file which is a new order and is added to the MWL with status scheduled, another HL7 file is loaded after procedure completion which changes the status of the order from scheduled to completed.

wondering if I am doing something wrong, please advise.

dicom.sql

Code

*WorkList*
{
     { 0x0008, 0x0050, "AccessionNumber",    16, SQL_C_CHAR, DT_STR,  "OBR.3" },
     { 0x0010, 0x0020, "PatientID",          64, SQL_C_CHAR, DT_STR,  "PID.4" },
     { 0x0010, 0x0010, "PatientName",        64, SQL_C_CHAR, DT_STR,  "PID.5" },
     { 0x0010, 0x0030, "PatientBirthDate",    8, SQL_C_DATE, DT_DATE, "PID.7" },
     { 0x0010, 0x0040, "PatientSex",         16, SQL_C_CHAR, DT_STR,  "PID.8" },
     { 0x0008, 0x0090, "ReferPhysician",     64, SQL_C_CHAR, DT_STR, "OBR.2" },
     { 0x0008, 0x0080, "Institution",     64, SQL_C_CHAR, DT_STR, "OBR.1" },
     { 0x0008, 0x1030, "StudyDescription", 64, SQL_C_CHAR, DT_STR, "OBR.9" },


     { 0x0010, 0x2000, "MedicalAlerts",      64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0010, 0x2110, "ContrastAllergies",  64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0020, 0x000d, "StudyInstanceUID",   64, SQL_C_CHAR, DT_UI,   "OBR.5" },
     { 0x0032, 0x1032, "ReqPhysician",       64, SQL_C_CHAR, DT_STR,  "OBR.16" },
     { 0x0032, 0x1060, "ReqProcDescription", 64, SQL_C_CHAR, DT_STR,  "OBR.4.1" },

     { 0x0040, 0x0100, "--------",   0, SQL_C_CHAR, DT_STARTSEQUENCE, "---" },
     { 0x0008, 0x0060, "Modality",           16, SQL_C_CHAR, DT_STR,  "OBR.21" },
     { 0x0032, 0x1070, "ReqContrastAgent",   64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0040, 0x0001, "ScheduledAE",        16, SQL_C_CHAR, DT_STR,  "OBR.8" },
     { 0x0040, 0x0002, "StartDate",           8, SQL_C_DATE, DT_DATE, "OBR.7.DATE" },
     { 0x0040, 0x0003, "StartTime",          16, SQL_C_CHAR, DT_TIME, "OBR.7.TIME" },
     { 0x0040, 0x0006, "PerfPhysician",      64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0040, 0x0007, "SchedPSDescription", 64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0040, 0x0009, "SchedPSID",          16, SQL_C_CHAR, DT_STR,  "OBR.4" },
     { 0x0040, 0x0010, "SchedStationName",   16, SQL_C_CHAR, DT_STR,  "OBR.24" },
     { 0x0040, 0x0011, "SchedPSLocation",    16, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0040, 0x0012, "PreMedication",      64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0040, 0x0020, "OrdrControl",        64, SQL_C_CHAR, DT_STR,  "ORC.1" },
     { 0x0040, 0x0252, "PProcedureSStatus",  64, SQL_C_CHAR, DT_STR,  "ORC.5" },
     { 0x0040, 0x0400, "SchedPSComments",    64, SQL_C_CHAR, DT_STR,  "---" },
     { 0x0040, 0x0100, "---------",    0, SQL_C_CHAR, DT_ENDSEQUENCE, "---" },

     { 0x0040, 0x1001, "ReqProcID",          16, SQL_C_CHAR, DT_STR,  "OBR.4.0" },
     { 0x0040, 0x1003, "ReqProcPriority",    16, SQL_C_CHAR, DT_STR,  "OBR.27 }
}

Display More

order.hl7

Code

MSH|^~\&|conquest|conquest|REC_APP|REC_FAC|200512301613||ORM^001|123456|P|2.0.0|||||
PID|1670|1234567897|1|ID0005|Patient^05||2005.05.05|M|||||||||||||||||||
PV1||||||||||||||||||||||||||||||||||||||||||||||||||
ORC|NW||2005-9999||SC||||200512301613||||||200512301613529400||||
OBR|S-05|RefPhy-05|0005|CR^Chest05|1.2.826.0.1.9876.2.404.20051230.2313529400.050505|200512301613529400|201903021205|SchAE-05|||||||||||||CR|||||||||||||||200512301613529400|

orderupdate.hl7

Code

MSH|^~\&|conquest|conquest|REC_APP|REC_FAC|200512301613||ORM^001|123456|P|2.0.0|||||
PID|1670|1234567897|1|ID0005|Patient^05||2005.05.05|M|||||||||||||||||||
PV1||||||||||||||||||||||||||||||||||||||||||||||||||
ORC|SC||2005-9999||CM||||200512301613||||||200512301613529400||||
OBR|S-05|RefPhy-05|0005|CR^Chest05|1.2.826.0.1.9876.2.404.20051230.2313529400.050505|200512301613529400|201903021205|SchAE-05|||||||||||||CR|||||||||||||||200512301613529400|

regards,

marcelvanherk · Mar 3rd 2019

Hi,

The HL7 code is quite dumb. You request will require a code change in dgate.cpp. Any worklist message is entered as follows, line 26452:

DB.AddRecord(WorkListTableName, fields, values);

This would need to be modified to e.g. first delete the existing record on accession number. The passed accession number can be caught close to line 26404.

Marcel

dumbterminal · Mar 3rd 2019

thankyou for the clarity. I was trying to see if an hl7 msg can put the MWL entry to completed status

marcelvanherk · Mar 3rd 2019

Hi,

of course you can use e.g. dgate --deleterecord: or lua scripting to delete the record for you.

Marcel

MWL entry update

Participate now!

Share