PCCPlan Minutes 2014 10 23: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 29: | Line 29: | ||
* Proposing to wire a machine readable workflow definition allowing for automation to produce the following | * Proposing to wire a machine readable workflow definition allowing for automation to produce the following | ||
** document the workflow | ** document the workflow | ||
**Conformance rules | ** Conformance rules | ||
** conformance tests | ** conformance tests | ||
** Implementation. | ** Implementation | ||
* Proposing that we develop FHIR resources in the IHE/FHIR workgroup that creates the workflow definition and task definition resources. Later we may need/want to create the workflow resource and the task resource. | |||
Revision as of 11:08, 23 October 2014
Attendees: Tone Southerland, Laura Heermann Langford, Keith Boone, Thom Kuhn, Anne Diamond, Charles Rica, Denise Downing,
Phone in Attendees: Emma Jones, Chris Lindop, John Donnelly, Guilia Pellizzon, Michael McCoy, Alex Lippet, members of PCD, John Feikema,
Remote Patient Monitoring - joint w/PCD (PCD webex)
Presented by Brian Reinhold and Jeff McGrath
- Review of the proposal.
- Determined most of the profile work is done. We would be looking at creating a workflow - not at the level of XDW, but more similar to our work in Perinatal workflow.
- Discussion RT work happening at HL7 in the PHR and FHIR that may have impact on this work.
- there is complete mapping to SNOMED for all the PCD data
Device Observation Semantic Bridge
Presented by Alex Lippit
- Review of the proposal and accompanying slide deck
- Discussion of PCD contributions (will serve up the content), PCC contributions (will identify the transactions) - Need a commitment for someone to do the mappings. VHA?
Workflow Resources/Framework
Presented by Keith Boone
- Review of work needed - but not a profile proposal.
- We have lots of work describing workflows with the essential requirements but the data is locked away in a PDF Document.
- There are several challenges with lot of reentry and and copy paste happening.
- XDW describes how to link a workflow definition but the workflow definition has not ever been defined.
- Proposing to wire a machine readable workflow definition allowing for automation to produce the following
- document the workflow
- Conformance rules
- conformance tests
- Implementation
- Proposing that we develop FHIR resources in the IHE/FHIR workgroup that creates the workflow definition and task definition resources. Later we may need/want to create the workflow resource and the task resource.