PCCTech Minutes 2017 11 15

From IHE Wiki
Jump to: navigation, search

IHE PCC Technical Minutes 11/15/2017 All Profile Proposals and evaluation matrix can be found at the FTP site: ftp://ftp.ihe.net/Patient_Care_Coordination/yr14_2018-2019/Technical%20Committee/Profile%20Proposals/




Time (US Central DST) Agenda Item Notes
Wednesday, November 15th
9:00 – 9:30 Introductions/Agenda Review/Sponsor Announcements by Jeremiah Myers, IHE Secretariat

New HIMSS Manager Lauren Groden introduced

New IHE members: Kala-ACOG, Michel Clifton-Epic

February F2F Meeting will be at the Univ of Oslo Feb 12-15, 2018

Public Comment April 30-4th at Oakbrook

Final Text Meeting will be July 16-20, 2018

IHE USA is requesting interested in writing blogs for HIMSS 2018

9:30 – 11:00 Emergency Transport to Facility Present: Andrea Fourquet (EHealth Sign), Lori Fourquet (EHealth Sign), Thom Kuhn (ACP), Michael Clifton (Epic), Amit Popit (Epic), Emma Jones (Allscripts), Kayla (ACOG), Denise Downing (AORN), Gila Pyke (Cognaissance)

Phone: Tone Southerland (IQVIA), Thierry Dart (ASIP Sante)

The problem: No proper transfer of information from an ambulance to a hospital A few of the mapping to NEMSIS are correct There are data detail concepts missing from the IHE profile. Need more data elements in each section Technical approach: Content profile- CDA summary document No new actors. Content creator and consumer are the existing actors for the profile. No new transactions. Andrea will have 2 new approaches. The biggest challenge to getting ems data is identifying the patient properly. The goal of the profile isn’t to take the human communication out of the equation but to simplify that communication and assist them in transferring the data from the ET to the facility.

New transaction added: FHIR update/create

Question for Joint Meeting – how do we identify a pt using FHIR without exchanging a document? PDQm will include demographics, use PIXm for not wanting to be exposed to demographics just one identifier

Discussion around this profile will have a new transaction FHIR update/create named Send EMS Transport Data, should this be a QEDm transaction, no the content is different,

ETS/ITS ITS is the same as ETS, but ITS doesn’t send scene data, this profile will deprecate the two existing PCC profiles ETS/ITS People are signing up at CA for ETS those individuals were asked to do RIP

HL7 document maps to EMS that is created for the hospital EMS Pt Care Report v2-origin started with creating a new CDA level 3 document and took all the NEMSIS content and created templates, currently there are no immunization content and international information i.e., insurance isn’t necessary for international purposes, HL7 took the NEMSIS value sets and normalize them with LOINC and ICD-9 codes ZOLL has been demonstrating this at CA with EPIC

Risks- confusion for implementation, CDA side cleaning up the work and harmonizing with HL7 work, non-international work want to profile it here, if it is international in nature go to HL7 to update Email Jay Lile or ask Dr Myers about the history of the NEMSIS HL7 Standard – NEMSIS - the goal of this profile is to use FHIR and NEMSIS is US based, so it doesn’t take into account international considerations, so make this content international

Use Case is focused on the hand-off from the ambulance to the HC facility and the exchange of the content, there will be a FHIR and CDA option for transmitting data and the underlining data standard HL7 EMS Pt Care Report Level 3, NEMSIS defined the data content and sponsored the CDA standard, the value sets are in VSAC (NLM)

Goal make it international

11:00 – 11:15 Break
11:15 – 12:30 CDA Document Summary Section Present: Thom Kuhn (ACP), Micheal Clifton (Epic), Amit Popit (Epic), Emma Jones (Allscripts), Denise Downing (AORN), Gila Pyke (Cognaissance)

Phone: Tone Southerland (IQVIA), Thierry Dart (ASIP Sante), Dr. Miller (HCO), Daniel Venton (Allscripts), Neelima (VA)

Problem – complaints from users (providers) the documents (CDA) they are receiving from other providers are too long need a concise summary Discussed existing standards available - IHE Document Section Summary (text), C-CDA 2.1 Notes Section (structured enteries) and sending PHI in the summary document and the document sitting in a repository, by creating this are we making the system generate a summary and stating the document was generated because someone queried because the document will become part of the pts medical record, this should only be a user generated summary

Next group of Use Cases is about Care Plan – there are linkages to the different sections within the CP, HL7 only gives examples of style sheets, but ONC is requiring a style sheet to be sent but the receiver should be able to view the content the way they want the information, displayed a better layout of the data showing the linkages of a concern, goal, interventions for one concern, systems can display or incorporate the data, the difference is the sender sends the summary or the receiver dynamically transform the data into a style sheet and displays the summary section

Discussion about making the profile into two+ profiles focusing one profile on provider>provider and then provider>system where the system generates the summary section Third Use Care - pulling and displaying structured content in the document into the Summary Section, there is fundamental issues with the HL7 standard because of deprecated problem sections that is being addressed

When writing the profile it will determine if the profile should be two profiles, currently there are no new actors, different transactions and options


12:30 – 1:30 Lunch
1:30 – 3:00 FHIR PlanDefinition for Care Planning Present: Thom Kuhn (ACP), Michael Clifton (Epic), Amit Popit (Epic), Chris Melo (Philips), Rafealle Gairdano (Arsenal Italy), Emma Jones (Allscripts), Denise Downing (AORN), Gila Pyke (Cognaissance)

Phone: Thierry Dart (ASIP Sante), Neelima (VA), Jeff Danford (Allscripts)

Dynamic CP profile was the created due to HL7 work, then in HL7 they started working on Care Coordination DAM Extend the DCP profile by providing the ability to use

Activity definitions will create an activity (i.e., medication) which will create the plan, it will use a FHIR workflow to create the plan FHIR Workflow Management – activity definition is a library for the plan definition, you put in the activity definitions as a predefined activity definition that is stored in a library

Rafealle – working on XDW, but not in ITI this cycle, their focus is to use FHIR to manage workflows, similar to this profile, but using general definitions, Task Resources

Question to the committee – is do we do the general workflow definition work with the specific (Care Plan) definition work? Mauro and Rafealla can offer guidance to this profile as SMEs

In January 2018 - Plan Definition turning into actionable orders will be tested at HL7 Hack-a-Thon which can be used to write IHE PCC volume 2


3:00 – 3:45 PCC Maintenance Work/CPs CP Maintenance

PCC TC rejected CP 266, with the proposal for the submitters to complete their next HL7 ballot and return with a new CP when the standard has passed ballot. Reviewed CP statuses/CP process. Began cleanup of CP folders.


3:45 – 4:30 Break
4:30 – 5:30 QRPH, ITI, PCC Joint Meeting Two (2) FHIR Profiles

Emergency Transport to Facility exchange of scene information from an emergency scene to a hospital, currently scene information, transfer information, and intervention are only available to hospitals on paper when the patient arrives, this profile will close that gap, EMS data can also be used for Quality Care Measures and QRPH is taking on this work which may contribute to the needed content in this profile so we will keep an eye on this work in QRPH (Trauma, STEMI, Stroke, etc…)

Plan Definition for Care Planning care planning is very difficult to create care plan, profiling the FHIR activity definition and Plan Definition Resources used by order sets or protocols, Extend the DCP profile by providing the ability to use


CDA Profile

CDA Document “Executive” Summary Section - that looks at several problems - CDA documents often contains large amounts of information that makes it difficult to identify pertinent information in an efficient way for the providers. This profile will provide a mechanism to provide a concise synopsis about the document that the author needs to communicate to the reader


5:00 Adjourn