PCCTech Minutes 2018 04 30
April 2018 F2F Meeting Day 1
Attendees: Steve Moore, MIR Tone Southerland, IQVIA Michael Clifton, EPIC Gila Pyke, Cognaissance Nemanja Mienkovic, ASIP Emma Jones, Allscripts Raffaele Giordano, Arsenal IT Celina Roth, HIMSS Yvonne, HIMSS Andrea Fourquet, eHealthsign Daniel Venton, Allscripts George Dixon, Allscripts Amit Popat, EPIC Chris Melo, Phillips Thomson Kuhn
|Discussion:
Agenda Update : Switched CDA Document Summary to start at 9:30am so that PCS Summary can be moved to the afternoon
Workflow CP Loinc Codes • Arsenal IT submitted 4 CPs proposing that we create our own TypeCode OIDs instead of waiting on LOINC to assign them, since LOINC does not manage non-clinical OIDs
• PCC will create 4 TypeCodes and update the consolidated IHE wiki where the formatCodes are with TypeCodes
• Gila will add this to the joint meeting agenda to help us understand how to assign typeCodes
CDA Document Summary • Emma presented CDA Document Summary volume 2, and updated the Template ID OIDs in the PCC Wiki • Emma will work with Tone offline to work out the Notes section and how to follow the CDA IG
Dynamic Care Plan (DCP) • FHIR based profile meant to support the care planning process • New actor, new transactions • Task still needs to be profiled • Gila to add “IHE Constraint Cardinality” column to the joint meeting agenda
IHE FHIR Profiles - Conformance (presenter John Moehrke) • Process menu item from Wiki left hand menu • FHIR Conformance Resource Templates contain guidance for profile writers who are using FHIR. What additional things can you do when profiling FHIR? This is just the current thinking, not the ultimate way we will profile FHIR as new IGs are published • You have to do this step for any of the publication systems so far o Process is described under “Current Guidance on ‘use’ of FHIR o A conformance resource is a way to convey metadata about datatypes, resources and API features of the FHIR spec that can be used to create derived specifications o Uses CapabilityStatement, StructureDefinition(s)(called profiles in simplifier), OperationDefinition, SearchParameter at minimum. Other Conformance module resources are still in flux. o John recommends that we use the STU3 Conformance resource as a manifest of the required elements • A capability statement is a definition of an actor • An implementation guide in HL7 is equivalent to a profile in IHE • A FHIR profile is a subset of StructureDefinition that puts constraints on a (single) resource, such as limiting the cardinality, defining the value set to be used, define fixed values, etc • Why should we publish them? o They are machine readable o There is tooling that has been built to help create the conformance resources o Conformance resources can be used by servers to test whether an app request is compliant with an IHE profile o There is also tooling for application writers to import definitions into their tooling, which will force them to fill out all the required fields • Wiki Profiles page really needs to be up to date!!! • Index of ftp.ihe.net/TF_Implementation_Material/fhir/CapabilityStatement/ contains machine readable capability statements where you can publish them • We then use “Simplifier” to publish them to the registry.fhir.org registry of conformance resources, which can point to the IHE wiki for the relevant profile. Anything mature should be updated to the FHIR registry • Publish examples of messages in the IHE domain implementation guide section of the implementation material wiki, not in the fhir directory which is limited to capability statements • Encourage IHE to get enterprise licenses to the Simplifier tool • TODO: All profile writers, upon completing their profile, to create a: o Capability Statement o Implementation Guide o Structure Definition(s) where you add constraints on a resource • Guidance on how to do this is on the wiki, and John is happy to help • Zulip, at chat.fhir.org is a group chat with an IHE stream that you can discuss any IHE topic. John can also use the announcements stream to announce public comment for FHIR IHE profiles
PCS Summary • Replace volume 2 with a statement “no new transactions” and delete everything • Reviewed volume 4 and vol 6 content