This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20161214"
Jump to navigation
Jump to search
(Created page with "{{subst::FHIR Workflow Template for Minutes}}") |
|||
| Line 8: | Line 8: | ||
==Attendees== | ==Attendees== | ||
| − | * | + | *Lloyd McKenzie (chair/scribe) |
| − | * | + | *Joe Lamy |
| + | *Johnathan Harber | ||
| + | *Jose Costa Teixeira | ||
| + | *Vassil Peytchev | ||
| + | *John Hatem - joined after refactoring workflow discussion | ||
| − | == | + | ==Observation & Event== |
| − | + | *Event.occurrence[x] maps to Observation.issued, not Observation.effective | |
| + | *Event.occurrence[x] maps to MedicationStatement.effective | ||
| − | + | That seems a bit different, but makes sense in terms of what's going on. As well, Observation and MedicationStatement status models look a bit different, but really are both talking about the progress of the event (i.e. capturing data for an Observation, taking a medication for MedicationStatement) | |
| − | |||
| + | ==Refactoring workflow== | ||
| + | Looked at the workflow page. Vassil will refactor, including adding examples and re-categorizing the scenarios as per his ballot comment. He may seek assistance adding examples once the refactoring is complete | ||
| + | |||
| + | ==Pattern QA== | ||
| + | Updated introductions to better differentiate between Definition/Event/Request and Task. Added text describing the difference between basedOn and replaces. | ||
| + | |||
| + | ==For future weeks== | ||
| + | * Volunteers to incorporate "example" material into workflow documentation (i.e. lab scenarios) | ||
| + | * Volunteers to map additional resources | ||
| + | * Work through QA criteria on resource patterns | ||
| + | * Continue to work through example scenarios | ||
| + | * Discussion of state machines for Task and Definition/Request/Event (with Vasil) | ||
==Adjournment== | ==Adjournment== | ||
Latest revision as of 22:45, 14 December 2016
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
- Approve Minutes Prior Meeting on mm/dd
Attendees
- Lloyd McKenzie (chair/scribe)
- Joe Lamy
- Johnathan Harber
- Jose Costa Teixeira
- Vassil Peytchev
- John Hatem - joined after refactoring workflow discussion
Observation & Event
- Event.occurrence[x] maps to Observation.issued, not Observation.effective
- Event.occurrence[x] maps to MedicationStatement.effective
That seems a bit different, but makes sense in terms of what's going on. As well, Observation and MedicationStatement status models look a bit different, but really are both talking about the progress of the event (i.e. capturing data for an Observation, taking a medication for MedicationStatement)
Refactoring workflow
Looked at the workflow page. Vassil will refactor, including adding examples and re-categorizing the scenarios as per his ballot comment. He may seek assistance adding examples once the refactoring is complete
Pattern QA
Updated introductions to better differentiate between Definition/Event/Request and Task. Added text describing the difference between basedOn and replaces.
For future weeks
- Volunteers to incorporate "example" material into workflow documentation (i.e. lab scenarios)
- Volunteers to map additional resources
- Work through QA criteria on resource patterns
- Continue to work through example scenarios
- Discussion of state machines for Task and Definition/Request/Event (with Vasil)
