Added
an important one – “Force multiplier”
r/Tim
703.304.4829
__________________________________________________________
Agree
with Dee.
So
the purpose of this is a teaser to hook people into coming
to our session/demo that evening, correct? We want a strong
hook with snippets of information.
My
suggesting is to focus on what is being demonstrated
and the benefits/problems being solved. Quick and dirty
litany – no order, grammar or word-smithing. Perhaps mod a
handful as snippets (Jeff/John?).
- Purpose
of demonstration:
§ Live
demonstration of EMS patient care and tracking information
flow from incident scene to hospitals
§ Day
to day and mass casualty real-time data exchange across
disparate systems and devices
§ Practical
use of practitioner-driven cross-SDO coordinated standards
(HL7, OASIS and others)
Emergency
Department physicians lack critical incoming patient
information 32% of the time
Yearly
approximately 114 million visits to EDs occur; 16 million
by ambulance
PROBLEMS
SOLVED
- Myriad
of state and local patient tracking systems that
don’t “talk”
- Lacking
information exchange between EMS and Emergency
Departments
- Resorting
to manual and slow patient information sharing
- Family
Stress - Notification and Reunification
BENEFITS
- “Force
Multiplier
- Incident
scene patient routing decision support, matching
patient needs with hospitals
- Advanced
hospital preparedness and
transition of care
- Improved
individual and care team experience
- Automated
EMS Emergency hospital evacuation tracking
- Timely
and accurate family notification and reunification
- Automated
EMS patient care data populates the HIE Electronic
Health Record (EHR)
- EMS
and acute care data increases the ability to analyze
first responder impact on quality outcomes
- Continue
current systems use without changes or training.
Build once/reuse
- Meets
intent of “Meaningful Use”
- OASIS
Emergency Data eXchange Language standards used:
(Not
sure we should even list them here)
- EDXL-DE
(spell out)
- EDXL-TEP
(spell out)
- EDXL-HAVE
(spell out)
- EDXL-TEP-v1.1
to HL7 Messaging Transformation Document
r/Tim
703.304.4829
__________________________________________________________
I
agree with Elysa that we want to focus on the OASIS-HL7 collaboration
in Tracking Emergency Patients (TEP by itself is
just another TLA), so I would spell it out.
Thanks,
Rex
On 8/4/2016 7:30 AM, Elysa Jones wrote:
I
suggest the text points be listed as:
Title:
Bridging….
When/where:
…
Purpose:
Demonstrate the use of the HL7-OASIS TEP joint release
bi-directional transformation document
OASIS
EDXL standards to be highlighted are: ….
HL7
messages are: …
I
think it is important to state our purpose to be the joint
document.
Thanks,
Elysa
Hi Everyone,
Here is our first pass at bullet points for the Call for
Participation for the HL&-Bof
Demonstration/Presentation:
- September
20, 2016, 5:15-6:15 pm, Constellation Ballroom D,
Hyatt-Regency Baltimore, Md
- Bridging
Emergency Patient Information Between Hospital Systems
and Emergency Services
- Purpose
of demonstration:
- Show
use of the following standards in a mass-casualty
scenario tracking emergency patient information flow
across different systems and devices
- EDXL-TEP-v1.1
to HL7 Messaging Transformation Document
--
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670