PCC TC Face to Face February 25-March 01, 2019 - Minutes

Day 1 - Monday 2019 2 25 - IHE PCC Tech Committee F2F RSNA Meeting

Participants: Emma Jones (Allscripts), Michael Clifton (Epic), Amit Trivedi(Himss), Thierry Dart (ASIP Santé) On Phone: Georges Dixon (Allscripts)

DCP - Dynamic Care Planning

DCTM - Dynamic Care Team Management

• [1]
• Volume 1
• DCTM is a workflow profile
• Open issue : Shall we combine DCP and DCTM together ?
• DCP profil have been updated to include a care team actor, uses cases, pregnancy plans...
• Volume 2 discussion : should the participant roles need to be collected when the care team is generated ?

CCG - Computable Care Guidelines

• Meeting with QRPH domain
• volume 1
• CCG is a Hight level collaboration between WHO, CDC and IHE Int. to
• Actors of DCP's profil have been incorporated in CCG
• CCG uses cases could be on HIV, diabetes, hypertension, …

Discussion and Documentation of Continuous Cycle

• PCC domain discuss on continuous development
• The proposal is to move to a model where new work items can be started at any point in the year. The three 5-day face-to-face working meetings in the first half of the calendar year, plus two 2-day selection meetings in the last calendar quarter, are replaced by four 5-day working meetings evenly spaced through the year.
• Governance and process are not changing
• PCC domain agree on:
  • Approved Projects must submit their developed work two weeks prior to Face-to-face meeting (call for proposals)
  • Approved Projects must progress. Any project that misses two face-to-face meetings in a row will be canceled
  • Projects will not progress each quarter -- more than one quarter without improvement shall be automatic termination of that project
  • Connectathon is based on face-to-face meeting at-least four months prior to Connectathon
• For DCTM and Keith's new proposals, as we have no call proposal, PCC domain will discuss
• Decisions
  • PCC domain will make a call for proposal for the Spring meetings (April 29 - May 3, 2019, Oak Brook IL)
  • PCC domain will schedule monthly calls to monitor progress on CPs and profils

New Business, other projects

• Most systems only use text section on CDA. End users only see the documents.
• The main problem is to better specifying content and uses of data instead of just rendering the data
• PCC RECON profil speaks about reconciliation uses cases. It gives concepts on reconciliation without technical details. RECON profil have not been tested at the connectathon
• How to make "data import from CDA" it testable for the connectathon ? Connectathon is a great place to do content tests.
• Should PCC write a guideline for data import from CDA document ?

Day 2 - Tuesday 2019 2 26 - IHE PCC Tech Committee F2F RSNA Meeting

Participants: Emma Jones (Allscripts), Michael Clifton (Epic), Amit Trivedi(Himss), Keith Boone (), Thierry Dart (ASIP Santé) On Phone: Georges Dixon (Allscripts)

Discussion on QEDm comment

• Participants: same + John Moehrke, Charles Parisot (GE)
• John Moehrke has posted a on QEDm in the PCC technical group (22th February 2019):
  • There are no constraints on the content of the QEDm resources.
  • It is good to have query parameters, but there are no constraints on the content. Such as requiring that Observations must use LOINC where ever possible. etc. See [US-Core profile|http://www.hl7.org/fhir/us/core/StructureDefinition-us-core-observationresults.html] for some good baseline constraints.
  • Is this lack of constraints intended or a missed opportunity to drive good quality FHIR Resource data?
• Resolution:
  • Make a document on minimal structure definitions, publish it
  • For the next F2F meeting
  • John will create the GitHub to import the current US court, start inviting other
  • Charles Parisot will send to have feedback from differents countries (US court, France, ...)

DCP-Dynamic Care Plan and DCTM-Dynamic Care Team management

• Summary of DCP profile
  • is a FHIR based profile to exchange care plans for a patient
  • is a "meta-profile"
• Summary if DCTM profile
  • is a profile to assign care team members to a patient to provide, care, care coordination ...
  • Care team should be structured, historical log of care teams. create a new care team resource when, it changes and make inactive the old one.
  • When a patient get discharged, the patient care team will be updated with the new members.
  • Could be in a single enterpr create a new care team resource whise and across enterprise
  • This profile is based on HL7's care Team DAM
• DCP profile work
  • DCP is a metaprofile that contains the DCTM actors and transactions. DCTM is a separate profile become some systems (like Scheduling systems) only managing.
  • CareTeam Service actor and Care Plan Service actor are kept separate
    • Because of complexity of Care plan deployment, different systems these two actors : care team service could be an administrative management and care plan service is a EMR system
  • CarePlan Contributor actor and Care team Contributor is Ok
• Security chapter have been updated
• Next steps : implements the changes and clean up the grouping