This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Infrastructure Minutes CC 20190114WGMQ4"
Jump to navigation
Jump to search
(→Agenda) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
[[:Category:2019 FHIR Infrastructure Minutes|Return to FHIR Infrastructure Minutes]] | [[:Category:2019 FHIR Infrastructure Minutes|Return to FHIR Infrastructure Minutes]] | ||
==Agenda== | ==Agenda== | ||
| + | * Introductions | ||
* Questions | * Questions | ||
* Alignment with workflow patterns | * Alignment with workflow patterns | ||
| Line 11: | Line 12: | ||
==Attendees== | ==Attendees== | ||
| − | + | ||
| − | + | See attendance log at bit.ly.?? | |
==Minutes approval== | ==Minutes approval== | ||
| − | * | + | *NA |
| − | ==Agenda | + | ==Agenda Items == |
| − | + | FHIR-I Monday Q4 Notes: | |
| + | '''Questions and Issues''' | ||
| + | |||
| + | * Question about maturity/stability of workflow artifacts: "No maturity levels on artifacts since not directly implemented but they do influence/change resources." patterns right at about FMM level 4 in stability | ||
| + | |||
| + | * Brief history of workflow project ( Patterns, state machines, Guidance pages, Task Resource ) ... | ||
| + | |||
| + | * Question about MessageHeader valuesets: "Messaging is confined to small set of trading partners but no impetus for standarding yet..." | ||
| + | |||
| + | * Issue with ImagingStudy: | ||
| + | ** Dicom imaging study can be created over time and even several encounters and does not map the 'event' pattern. Is it close enough? | ||
| + | ** to be discussed in quarter with II. | ||
| + | |||
| + | * Question about Task workflow state machine: Task is in rejected state still can be cancelled. Can create a gforge request to clarify | ||
| + | |||
| + | * Workflow project scope includes how messaging occurs within a particular pattern. | ||
| + | |||
| + | '''Tasks for R5 cycle:''' | ||
| + | # Review alignment with workflow patterns. | ||
| + | ## Plan to incorporate new qa functionality into build tooling to generate warning/errors if not mapped correctly to patterns | ||
| + | |||
| + | #Implement ExampleScenario Resource ( draft resource ) designed to provide set of example instance that follow a workflow pattern. | ||
| + | ## seeking partner to implement in real world scenario/use case -( no interest expressed in room). | ||
| + | # Task Resource owned by OO and goal is to make it FMM3-FMM4 | ||
| + | ## discuss Task issues on workflow calls - Monday 2PM Eastern (Orders and Observation make use call to dispose of trackers) | ||
| + | # Creation of multiple example instances for each resources | ||
| + | # Workflow Connectathon: Question of Interest and no current plan | ||
| + | Task is showing up in various implementation such as DaVinci CRD. | ||
==Adjournment== | ==Adjournment== | ||
Latest revision as of 03:36, 15 January 2019
FHIR Infrastructure WGM Monday Q4 (Date above)
Return to FHIR Infrastructure Minutes
Agenda
- Introductions
- Questions
- Alignment with workflow patterns
- Community interest in exercising workflow patterns
- Example Instances
Attendees
See attendance log at bit.ly.??
Minutes approval
- NA
Agenda Items
FHIR-I Monday Q4 Notes:
Questions and Issues
- Question about maturity/stability of workflow artifacts: "No maturity levels on artifacts since not directly implemented but they do influence/change resources." patterns right at about FMM level 4 in stability
- Brief history of workflow project ( Patterns, state machines, Guidance pages, Task Resource ) ...
- Question about MessageHeader valuesets: "Messaging is confined to small set of trading partners but no impetus for standarding yet..."
- Issue with ImagingStudy:
- Dicom imaging study can be created over time and even several encounters and does not map the 'event' pattern. Is it close enough?
- to be discussed in quarter with II.
- Question about Task workflow state machine: Task is in rejected state still can be cancelled. Can create a gforge request to clarify
- Workflow project scope includes how messaging occurs within a particular pattern.
Tasks for R5 cycle:
- Review alignment with workflow patterns.
- Plan to incorporate new qa functionality into build tooling to generate warning/errors if not mapped correctly to patterns
- Implement ExampleScenario Resource ( draft resource ) designed to provide set of example instance that follow a workflow pattern.
- seeking partner to implement in real world scenario/use case -( no interest expressed in room).
- Task Resource owned by OO and goal is to make it FMM3-FMM4
- discuss Task issues on workflow calls - Monday 2PM Eastern (Orders and Observation make use call to dispose of trackers)
- Creation of multiple example instances for each resources
- Workflow Connectathon: Question of Interest and no current plan
Task is showing up in various implementation such as DaVinci CRD.
