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

Tim Grapes

SE Solutions, Inc.

(703) 304-4829

From: Mears, Greg D [mailto:greg_mears@med.unc.edu]
Sent: Wednesday, March 21, 2012 11:47 AM
To: Grapes, Timothy
Subject: Re: NEMSIS and HL7
Importance: High

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

________________________________

Greg Mears, MD

Associate Professor

Director of Innovation

Department of Emergency Medicine

University of North Carolina-Chapel Hill

919-672-9630

gdm@med.unc.edu

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

Tim Grapes

SE Solutions, Inc.

(703) 304-4829

From: Mears, Greg D [mailto:greg_mears@med.unc.edu]
Sent: Friday, November 04, 2011 4:13 PM
To: Grapes, Timothy
Subject: Re: NEMSIS and HL7

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

________________________________

Greg Mears, MD

Associate Professor

Director of Innovation

Department of Emergency Medicine

University of North Carolina-Chapel Hill

919-672-9630

gdm@med.unc.edu

On Nov 3, 2011, at 5:31 PM, Grapes, Timothy wrote:

Dr. Mears,
How might I gain access to look at the results of you efforts to
integrate NEMSIS into HL7? Is there an on-line library or portal of
some sort?

Thanks,
Tim
Tim Grapes
SE Solutions, Inc.
(703) 304-4829

-----Original Message-----
From: Mears, Greg D [mailto:greg_mears@med.unc.edu]
Sent: Thursday, November 03, 2011 2:31 PM
To: Grapes, Timothy
Subject: Re: Update on EDXL-TEC, TEP, HHS, OASIS & HL7 collaboration

Thanks Tim,

Good to see movement!

Thumb typed with creative spell-checking.

Greg
_________________________
Greg Mears, MD
Associate Professor

Director of Innovation
Department of Emergency Medicine
University of North Carolina-Chapel Hill
919-672-9630
gdm@med.unc.edu

On Nov 2, 2011, at 10:32 PM, "Grapes, Timothy"
<Timothy.Grapes@sesolutions.com> wrote:

Ladies and Gentlemen,

This note is intended to provide an update on recent progress made on

the EDXL-Tracking of Emergency Clients (TEC) effort, as well as recent
progress and coordination with HHS regarding EDXL-TEP.

EDXL-Tracking of Emergency Clients (TEC)

Although a few additional comments have recently been received and are

under review, essentially the EDXL-TEC effort has completed and
published one of two primary deliverables, the Project Initiation
Document (PID). The purpose of the PID is to gain consensus on the
purpose, objectives, and scope of the EDXL-TEC standard, and sets the
foundation for the detailed Requirements and draft Messaging
Specification, which will be submitted into the Standards Development
Organization (SDO) for publication. The PID will act as a "living
document", refined as project scope is refined, and will continue to
feed into the current design process.

EDXL-Tracking of Emergency Patients (TEP)

As always, requirements driven from EDXL practitioner efforts will be

met through publication of open, international standards that are free
to use for data exchange systems interoperability across jurisdictions,
professions and systems. This program continues to work closely with
U.S. federal partners to ensure that the resulting standards meet
requirements for data exchange with state and local partners. During
the month of October 2011, the program met again with HHS to ensure that
mutual efforts are in lockstep in support of national patient tracking
direction and the framework being set forth by HHS and the Senior
Leadership Council on Patient Tracking. This includes TEP standard
alignment to fill the gap for a national patient tracking standard, to
enable data exchange between various state and local systems and the HHS
NDMS national patient tracking system: the Joint Patient Assessment &
Tracking System (JPATS).

TEP champion states of Tennessee, Maryland and Louisiana with DHS

support met with NDMS-JPATS staff in October to review history and share
status of mutual efforts. The meeting reiterated and clarified the fact
that the TEP effort is facilitating definition of the data exchange
standard, but does not specify a specific solution, architecture or
mechanism for transport (sending and receiving) of TEP standard-based
XML messages. Where the federal government may be involved in the
process of patient movement, tracking and data exchange with their state
and local partners, solution architecture and mechanism for transport of
TEP standard-based patient tracking information will be determined by
HHS in collaboration with their state and local partners.

Successful outcomes of that meeting resulted in an invitation for DHS

to present TEP to the Senior Leadership Council on Patient Tracking,
comprised of decision-makers across cooperative agencies in support of
ESF-8, NDMS and patient tracking. The TEP presentation by Mr. Denis
Gusty was well received, and questions focused on process and plans for
moving forward. A meeting with the HHS Office of the National
Coordinator (ONC) will be scheduled in the near future, to ensure that
all appropriate ESF-8 agencies and organizations with federal authority
over patient tracking processes are cognizant and participate to the
full extend desired.

Finally, EDXL-TEP standard development is currently in process, and

will be developed in collaboration between OASIS and HL7 per signed
agreement. This approach recognizes the potential value of TEP not only
in emergency response and management data exchanges, but also for
receipt by hospitals to assist with visibility of incoming patients to
support early preparation. This agreement and collaborative approach
again helps to maximize adoption and ultimate value of the TEP standard
through re-use and adherence to existing taxonomies used by hospitals
today. The CTO of HL7 has been designated as the HL7 primary POC, and
a meeting will be scheduled in the near future to finalize this
collaboration process and specific outcomes.

Please don't hesitate to contact me with any comments or questions.

Very Respectfully,

The DHS EDXL Messaging Standards Support Team Tim Grapes SE Solutions,

Inc.

(703) 304-4829

<SrLeadersCouncilOnPatientMovement-TEPv1 2.pptx>

<HHS-StatesOct2011MeetingMemoOfAgreement.docx>

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1834 / Virus Database: 2092/4593 - Release Date:
11/03/11

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1869 / Virus Database: 2092/4595 - Release Date: 11/04/11

______________________________________________________________________
This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus
______________________________________________________________________

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2114/4884 - Release Date: 03/21/12

emergency-tep message