FW: NEMSIS and HL7

Looks like we definitely need an end-around from John Quinn, or an HL7 membership…

Thanks,
    Tim

Tim Grapes

SE Solutions, Inc.

(703) 304-4829

 

From: Mears, Greg D [mailto:] 
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



 

 

 

 

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:] 
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


On Nov 2, 2011, at 10:32 PM, "Grapes, Timothy"
<> 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