Re: [MT-L] 6.x Lab: IMO & LOINC ( MIS.NMAP Push LOINC from M-AT to NPR ) IMO0001 & IMO0002
Julie.Matheson
Oh Interesting love to learn new tricks do we need to request the fix from IMO or MEDITECH ( we are 6.08 pp22 )
Currently working in the MapIT Tool for IMO 2.0 and finding numerous instances of the IMO0001 & IMO0002 Codes on existing mapping that we are adjusting now.
FYI IMO 2.0 – We mapped IMO in the MapIT tool several years ago and reconciled into MEDITECH / since then have been manually looking up IMO codes utilizing the function Alicia posted (by typing LOINC####-#IMO )
For new builds and as we LAB folks know the sendouts constantly have new builds and changes. IMO 2.0 involves extracting files sending to IMO to load into MapIT to run a check on existing mapping and identify areas needing updates. The >1 LOINC feature in MapIT now pulls the IMO0001 & IMO0002 in additional to terms with more than one LOINC and is a great tool for identify what needs to be re-mapped.
If we can get this fix into MEDITECH the issue of picking the wrong IMO can be avoided ( keeping in mind Paul’s advice I’ll be using that as well to avoid this in the future – Paul’s post mentioned utilizing LOINC.org in combination with the lookup in MEDITECH )
Thank You,
Julie…
Julie A. Matheson
Professional Healthcare IT Specialist
Independent MEDITECH Clinical Consultant
Office: 774-254-4433 (EST)
Email: Julie.M...@comcast.net
From: Goode, Derrick [mailto:DIG...@phhealthcare.org]
Sent: Wednesday, May 31, 2017 8:59 AM
To: 'Paul Goedicke'; 'Alicia Poznanovich'; 'MathesonJulie'; 'Britt Watters'
Cc: Julie.M...@comcast.net; Matheson...@comcast.net
Subject: RE: [MT-L] 6.x Lab: IMO & LOINC ( MIS.NMAP Push LOINC from M-AT to NPR
FYI
IMO has a fix they can put in to block all invalid LOINC (IMO0001 and IMO0002) Codes.
Derrick Goode
Clinical Informatics
Penn Highlands Elk
763 Johnsonburg Rd.
St. Marys, PA 15857
814-788-8661 Telephone
814-788-8076 Fax
Helpdesk: help...@phhealthcare.org
From: Meditech-l [mailto:meditech-...@mtusers.com] On Behalf Of Paul Goedicke
Sent: Tuesday, May 30, 2017 8:02 PM
To: 'Alicia Poznanovich'; 'MathesonJulie'; 'Britt Watters'; medit...@mtusers.com
Cc: Julie.M...@comcast.net; Matheson...@comcast.net
Subject: Re: [MT-L] 6.x Lab: IMO & LOINC ( MIS.NMAP Push LOINC from M-AT to NPR
When doing a LOINC lookup for the IMO map, you may be presented with a list to pick from, some of which may still be linked to an invalid LOINC (IMO0001). It’s best to view the LOINC description on loinc.org to make sure you pick the correct one. It is improving, as IMO is finally including the actual loinc.org description, and the format is obvious when you’re used to seeing them, so you select the correct one from the lookup.
Paul
From: Alicia Poznanovich [mailto:apozna...@svmh.com]
Sent: Tuesday, May 30, 2017 2:44 PM
To: 'MathesonJulie' <Mathes...@comcast.net>; 'Britt Watters' <bwat...@bartletthospital.org>; medit...@mtusers.com
Cc: pgoe...@cableone.net; Julie.M...@comcast.net; Matheson...@comcast.net
Subject: RE: [MT-L] 6.x Lab: IMO & LOINC ( MIS.NMAP Push LOINC from M-AT to NPR
Yes, the only way I search for an IMO code now is by using the LOINC code search. If the LOINC code is 101-2, then you can search for an appropriate IMO by typing LOINC101-2IMO into the Nomenclature field in the test dictionary.
Thank you,
Alicia Poznanovich
LIS Coordinator
Salinas Valley Memorial Hospital
From: MathesonJulie [mailto:Mathes...@comcast.net]
Sent: Tuesday, May 30, 2017 12:39 PM
To: Alicia Poznanovich; 'Britt Watters'; medit...@mtusers.com
Cc: pgoe...@cableone.net; Julie.M...@comcast.net; Matheson...@comcast.net
Subject: RE: [MT-L] 6.x Lab: IMO & LOINC ( MIS.NMAP Push LOINC from M-AT to NPR
Hi All,
Paul and I posted this a few years ago and have found this still comes up for 6x sites (Give this a read and if I can answer any questions reply to all so the group can be on the thread)
See details below hope this helps. In regards to outbound HL7 and HIE the LOINC from the IMO MIS NMAP should be in the HL7 if the hospital is utilizing MEDITECH’s program request this feature
As it may need to be turned on or an updated HL7 is needed. Have done this and seen in the LOINC from the IMO send in the HL7 – If however the LOINC in the NMAP is missing the system will then look
To the LOINC filed in the TEST Dx and this is where things get confusing. Although it is blank try removing the IMO and see if the LOINC field shows up again ( keep in mind you want the LOINC from the NMAP but because of the “PUSH” issue described below it may not be there on the NPR side but you will see it in the NMAP M-AT side. OK enough info for now give below a read J
Thank You,
Julie…
Julie A. Matheson
Professional Healthcare IT Specialist
Independent MEDITECH Clinical Consultant
Office: 774-254-4433 (EST)
Email: Julie.M...@comcast.net
From: Paul Goedicke
Sent: 12/26/2014 1:03:06 PM (GMT)
Subject: [MT-L] all platforms IMO mapping
A friend asked me to share this with the list. Some of the information she discovered while working as a consultant, and some I have discovered also working with other sites as well as our own.
6.x IMO load process - the codes reside in BOTH the M-AT Focus side Nomenclature IMO AND NPR MIS.NMAP Nomenclature IMO (LAB is still NPR in 6.x)
Normal process is to load into the M-AT Focus side, then COPY/PUSH them to the NPR MIS.NMAP side. It has been discovered this process has resulted in missing codes in the NPR MIS.NMAP side. After delays until finding someone at Meditech who understood what she was talking about, the solution was to have Meditech PUSH/COPY (note the order) the codes from M-AT to NPR. The good news is once the PUSH is completed and all the background jobs for the COPY are caught up, it appears to resolve the issue. The bad news is this issue has been identified at other 6.x sites.
The other issue she and I have identified is with the scale type of LOINC - if the scale type of the LOINC is not correct, it will create issues with your electronic lab results interfaces. Numeric tests would normally have a LOINC with a Qn type and a non-numeric should not have a Qn type LOINC code. A Qn type code will send the reporting units to the interface. It may require re-thinking things like urine dipstick tests where the test is non-numeric, but the result codes may be numbers. If the reporting units are entered in the test dictionary, they will not transmit with results if an Ord type LOINC code is attached. An example would be 100 mg/dL protein - if the result code text is 100, the interface will only show the 100, without reporting units, if it is mapped to an Ord type LOINC.
One last thing - if anyone mapped tests or procedures to IMO0001 or IMO0002 codes, you'll find those have no embedded LOINC or SNOMED code, which will cause issues when sending results through an HL7 2.5.1 interface.
If you're only fixing these issues as they create problems through the interfaces, you're probably missing quite a few. A lot of this information would really have been useful 12 months ago when most sites were struggling.
IMO was not the helpful tool it was presented as and I only do mapping directly from the dictionary fields now, using the appropriate code (LOINC or SNOMED) and performing a lookup into IMO using the specific code. Simply doing a terminology lookup into IMO is no guarantee the correct code (i.e. scale type for LOINC) is being attached.
We thought it was important to share this information to help those struggling and to allow others to verify their setup before it causes issues.
Thanks to Julie Matheson for sharing her experience and information.
Paul Goedicke
Clinical Analyst III
Jackson County Memorial Hospital
1200 East Pecan
Altus, OK 73521
(580)379-5565
paulgo...@jcmh.com
I hope to be the kind of person my dog thinks I am.
- anonymous
The documents accompanying this transmission contain confidential information, belonging to the sender, that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information after its stated need has been fulfilled.
If you are not the intended recipient, you are hereby notified that any reading, disclosure, copying, distribution, or action taken in reliance on the contents of these documents is strictly prohibited. Violators may be prosecuted. If you have received this email in error, please notify the sender immediately and destroy the transmitted information.
From: Meditech-l [mailto:meditech-...@mtusers.com] On Behalf Of Alicia Poznanovich
Sent: Friday, May 26, 2017 12:49 PM
To: 'Britt Watters'; 'medit...@mtusers.com'
Subject: Re: [MT-L] 6.x Lab: IMO & LOINC
Try putting your IMO code in the “Nomenclature Map” field for the specific method. Our IMO code is in both spots & we don’t have any problems with our PHI.
Thank you,
Alicia Poznanovich
LIS Coordinator
Salinas Valley Memorial Hospital
From: Britt Watters [mailto:bwat...@bartletthospital.org]
Sent: Wednesday, May 24, 2017 12:08 PM
To: 'medit...@mtusers.com'
Subject: [MT-L] 6.x Lab: IMO & LOINC
To LOINC or not to LOINC….
We implemented 6.14 in 2015 and used IMO to populate the Default Nomenclature field in the Lab & MIC dictionaries. We are now implementing the PHI (Lab Results) interface, and our state HIE is requesting the LOINC code in the interface message. The LOINC field is inaccessible in the dictionaries because the default Nomenclature field is populated. The advantage to using IMO was to avoid having to define a separate LOINC code for everything needed for interoperability. The IMO nomenclature code has a LOINC code embedded, which can be seen in the Nomenclature Map Dictionary for most tests and procedures.
We haven’t tested the interface yet, but our HIE is skeptical about the LOINC code being accessible in the message, and are saying we need to either populate the LOINC field, or do a custom in the interface to look at the test name instead. Adding the LOINC code to the dictionaries would entail removing the Default Nomenclature field contents and defining the fields by Method instead. A lot of work!
I’d be interested in hearing from sites using IMO and also sending Lab results out to an HIE or other vendor.
Thank you!
Britt Watters, BSMT(ASCP)
Laboratory Systems Analyst
Bartlett Regional Hospital
P 907.796.8643 |F 907.796.8466
CONFIDENTIALITY NOTICE: This message and any included attachments are from Salinas Valley Memorial Healthcare System and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Salinas Valley Memorial Healthcare System's Privacy Officer in Salinas, California, U.S.A. at (+1) (831) 755-0751.
CONFIDENTIALITY NOTICE: This message and any included attachments are from Salinas Valley Memorial Healthcare System and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Salinas Valley Memorial Healthcare System's Privacy Officer in Salinas, California, U.S.A. at (+1) (831) 755-0751.
This email and any attached files are sensitive in nature and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of Penn Highlands Healthcare or its affiliates.. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.