ORU into Logician

[Mark Perschbacher]

We have started working with Logician to build a result interface for our pathology system.  Our current system takes the text based reports, and parses them into the ORU assigning each line of text, and blank lines, each own OBX.  I sent a result over to them, and Logician does not seem to have any features for stripping out extraneous characters or blank segments.  The programmer I was working with suggested changing the message type to MDM or from OBX to an NTE.  Has anyone run across similar problems with Logician?

Topic

[Mike Grieger]

Which message type you create depends on how the data is importing into Logician.  You have a choice between coming in as Lab results, or as Test Documents.  Lab results can populate flow sheets, documents cannot.  Or if your organization thinks they want to have the results as a report, but also be able to trend using flowsheets, you could create a message for each.

I would guess that you would just want the text result, so that would be the MDM message.  Logician does have some pretty good interface specs – that would be the place to start.

[Mark Perschbacher]

I am not familiar with MDM’s, but will see what I can find out about them.  What I would be looking at is converting the ORU with multiple OBX’s for each line of text to an MDM.  Any thoughts about how to accomplish this?

[Mike Grieger]

Just want to make sure that I’m understanding the system you are talking about, as the name has changed on the one I’m referring to.  It was Logician (previously owned by Medicalogic), but GE has acquired and is now called Centricity EMR.  That the one?

If so, there are probably several ways to approach this, in tcl, in the Xlate through iteration…   however, do you even need to worry about it?  The interface task setup in the app gives the flexibility to take multiple OBX segments.  Our source systems have all the text in one, so I haven’t played around with this scenario, but it would certainly be worth a shot.

[Mark Perschbacher]

I think we are talking about the same system.  I have just started working with this vendor, but it is GE.  The programmer I was working with didn’t seem to share your opptimisitic view.  They were able to import all the OBX messages, however any blank line in the message pulled in the OBX-3, and a “No Reported Value” message from Centricity, really ugly.

[Mike Grieger]

The problem you see with the ‘no reported value’, etc, is still due to sending the results into Logician as a Lab result.  (I’m guessing you still are using the ORU^R01 message, and feeding it in through a Lab Result import task in Logician).  You should consider using the Documents import task, then feeding message type MDM^T02.  A check box in your interface task in Logician can allow for multiple OBX segments.

If you need further pointers, you can email me at michael.grieger@meritcare.com

[Robert Hamden]

You can do 1 of 2 things:

use an NTE segment for the result (NTE can contain up 64K) as follows:

MSH|^~&|MIC|COM|||200703091301||ORU|22615..LAB.QA1|P|2.1|||AL

PID|1||J000007392|J7498|LAB^FIVE^FORE||19650408|F|||108 PARK PLACE^^NASHVILLE^TN^37203||NONE|(615)259-8800||S||J00008233176

PV1|1||^^^HCA

OBR|1|M31667^MIC|^MIC||R||200703090800|||SO|||TEST|200703091255|THROAT|1CSLWR3650||Micro||||200703091301

NTE|||Specimen #: 07:QAX:B0000837R~

OBX|||||||||||||||^^^ML^QA1

OBR|2|M31667^MIC|^MIC|GRAMST^GRAM STAIN^L|R||200703090800|||SO|||TEST|200703091255|THROAT|1CSLWR3650||Micro||||200703091301|||F

NTE|||Micro~

OBR|3|M31667^MIC|^MIC|GRAMST^GRAM STAIN^L|R||200703090800|||SO|||TEST|200703091255|THROAT|1CSLWR3650||Micro||||200703091301|||F

NTE|||Micro~

NTE|||RP1.1    GS    2L            N

NTE|||RP1.2    GS    2+            N

NTE|||RP1.3    GS    GRAM STAIN            N

NTE|||RP2.1    GS    GPCL            N

NTE|||RP2.2    GS    GRAM POSITIVE COCCI            N

NTE|||RP2.3    GS    GRAM STAIN            N

OBR|4|M31667^MIC|^MIC|THROATC^THROAT CULTURE^L|R||200703090800|||SO|||TEST|200703091255|THROAT|1CSLWR3650||Micro||||200703091301|||F

NTE|||Micro~

OBR|5|M31667^MIC|^MIC|THROATC^THROAT CULTURE^L|R||200703090800|||SO|||TEST|200703091255|THROAT|1CSLWR3650||Micro||||200703091301|||F

Or convert the the ORU to an MDM message formated as follows:

MSH|^~&|ChartScript||||19981102111100||MDM|1|P|2.2|||NE||

EVN|T02|19981103091100||||

PID|1||MR-000-080||Test^Patient^A||19460818|F|||^^^^^||||||||999-34-6667

PV1|1|R|E IM||||smitchell

TXA|2|PA|TX|19981102111100||19981103091100|19981102111100|||||||169-5|2||AU|UC|AV|||hwinston^^^^^^^^^^^^^^19981103140742|

OBX|0001|TX||1|Pathology Report: Pap Smear~~Squamous and endocervical cells are seen in sufficient quantity. Estrogen is normal for this pt’s age and history. No inflammation is present. A normal bacterial flora is present.  PAP Smear is Class 1.~~V. Krishnatmurthy MD, Pathology.||||||||||

You can download the C-EMR specs at http://support.medicalogic.com

You will need a login and password.

[Author]

Replies