[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: NEMSIS and HL7
All, Please see the string below and attachment. Haven’t reviewed yet, but hope this will fill my initial action item to acquire to result of the NEMSIS integration with HL7. One of our steps is to use this to map to equal elements in the draft TEP schema, and determine where and how we should re-use those elements verbatim. This will also smooth upcoming collaboration and review with HL7 SME’s for the same purpose. Thanks, Tim Grapes SE Solutions, Inc. (703) 304-4829 From: Mears, Greg D [mailto:greg_mears@med.unc.edu] Hi Tim, This is great news that the agreement has been signed. NEMSIS has been moving forward within HL7. There is a DAM and a DIM that have passed ballot. We have recently obtained approval for a CDA based on NEMSIS that is at the Draft Standard for Trial Use (DSTU) stage. We have a few vendors that are starting to develop with it but nothing in production yet. Attached is the NEMSIS CDA implementation guide. There are documents for the DAM and DIM as well but I don't think they would be of great value to you at this point. The use of the EDXL-DE would be great from a messaging perspective within HL7. That is exciting to hear. Let me know if you have any other questions or need more info. Take care,
________________________________ Greg Mears, MD Associate Professor Director of Innovation Department of Emergency Medicine University of North Carolina-Chapel Hill 919-672-9630 On Mar 21, 2012, at 9:33:AM:EDT, Grapes, Timothy wrote: Hi Dr. Mears, I have a quick update and a follow-up request. I believe you have been on past updates through the SWG email list and I am planning to send another soon. First the request – Since I didn’t follow up with HL7 yet, I now have an urgent need for a copy, draft or otherwise, of the NEMSIS/HL7 Version 3. Are you able to forward a copy to me informally? I do not have an HL7 membership, but can go that route now if I must. The urgency is the TEP work moving forward in collaboration between OASIS and HL7. OASIS is moving toward a technical draft that represents the requirements, certain re-use structures they recommend (e.g. location, contact info etc.). We want to do a pre-mapping again against NEMSIS/HL7 as we enter working sessions and review with HL7, to streamline the process and also demonstrate the common desire to adopt/re-use vs. reinvent. An update to ensure we are communicating: We have made great progress on two fronts for TEP, and have agreements and process in place to complete the data exchange standard. Keep in mind this only focuses on the standard. Strategy for other components such as message broker, infrastructure etc. will be determined by HHS. My hope is that we can participate in those discussions because we have a great deal of experience with what does and does not work, but I don’t know that we’ll have a seat. First, the federal side: 1. The Sr. Leadership Council on Patient Movement agreed that with TEP as the data exchange standard component in support of the HHS national strategy for patient movement during disasters where ESF-8 assistance is required. They only requested circle-back with ONC (Office of the National Coordinator), which we have done. 2. ONC – We have met with Dr. Doug Fridsma, HHS Dir. Of Standards and Interoperability, and Dr. Lauren Thompson, Dir of the Federal Health Architecture (FHA). They agree with the approach and wish to assist where appropriate to help connect with “best sources” where components of TEP may already be defined. They also wish to assist with incentives (grant language if not mandates) for the adoption of TEP. 3. HHS-NDMS (and JPATS system) have been on-board and participated in all of the above 4. At the May ITS, HHS-NDMS (JPATS) have partnered with MD, TENN and Louisiana Region 7 on a joint panel and demonstration Second, the SDO side: 1. Following the formal agreement signed by HL7 and OASIS, the two organizations met for a full day a few weeks back (I attended). Agreement was reached to intertwine each SDO process details required, reviews/balloting, and HL7 will assist in the marketing and adoption of TEP with their constituencies. 2. To my surprise, they even recommend EDXL-DE as the common “wrapper”/routing method for all, saying that HL7 really does not have a common method. Happy to talk anytime – just let me know. Thanks, Tim Grapes SE Solutions, Inc. (703) 304-4829 From: Mears, Greg D [mailto:greg_mears@med.unc.edu] Hi Tim, NEMSIS Version 3 has been successfully balloted into HL7 as a CDA. They are working now to finalize the documentation and release it for Trial Use. I believe their target is January. If I see anything, I will send it your direction. If you have a membership in HL7, you can probably access the ballot documentation if you want to see something sooner. Take care,
________________________________ Greg Mears, MD Associate Professor Director of Innovation Department of Emergency Medicine University of North Carolina-Chapel Hill 919-672-9630 On Nov 3, 2011, at 5:31 PM, Grapes, Timothy wrote: Dr. Mears, Ladies and Gentlemen,
the EDXL-Tracking of Emergency Clients (TEC) effort, as well as recent
under review, essentially the EDXL-TEC effort has completed and EDXL-Tracking of Emergency Patients (TEP)
met through publication of open, international standards that are free
support met with NDMS-JPATS staff in October to review history and share
to present TEP to the Senior Leadership Council on Patient Tracking,
will be developed in collaboration between OASIS and HL7 per signed
Inc.
No virus found in this message.
No virus found in this message. |
Attachment:
EMSRunReportCDA_Dec2011.pdf
Description: EMSRunReportCDA_Dec2011.pdf
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]