This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20160928"
Jump to navigation
Jump to search
(Created page with "{{subst::FHIR Workflow Template for Minutes}}") |
|||
| Line 5: | Line 5: | ||
[[:Category:FHIR Workflow Minutes|Return to FHIR Workflow Minutes]] | [[:Category:FHIR Workflow Minutes|Return to FHIR Workflow Minutes]] | ||
==Agenda== | ==Agenda== | ||
| − | |||
==Attendees== | ==Attendees== | ||
| − | * | + | *Lloyd McKenzie (chair/scribe) |
| − | * | + | *Hans Buitendijk |
| − | + | *John Hatem | |
| − | + | *Kevan Riley | |
| − | + | *Karl Holzer | |
| − | + | *Vassil Peytchev | |
| − | + | *Chethan Makonahalli | |
| − | + | *Johnathan Harbor | |
| + | ==Vassil's tracker item== | ||
| + | * Discussion about [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11492 11492] | ||
| + | * Vassil feels that Task should always be required | ||
| + | * Discussion about scenarios where Task may be not be necessary | ||
| + | * Discussion about distinction between Task and Request pattern | ||
| + | * Vassil feels strongly that "workflow" should only be used for complex exchanges that track state. Others don't feel that state tracking or complexity is necessary | ||
| + | * Vassil feels that Task should be required or at least should be "preferred" | ||
| + | * Will resume discussion next week | ||
==Adjournment== | ==Adjournment== | ||
Latest revision as of 19:06, 28 September 2016
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
Attendees
- Lloyd McKenzie (chair/scribe)
- Hans Buitendijk
- John Hatem
- Kevan Riley
- Karl Holzer
- Vassil Peytchev
- Chethan Makonahalli
- Johnathan Harbor
Vassil's tracker item
- Discussion about 11492
- Vassil feels that Task should always be required
- Discussion about scenarios where Task may be not be necessary
- Discussion about distinction between Task and Request pattern
- Vassil feels strongly that "workflow" should only be used for complex exchanges that track state. Others don't feel that state tracking or complexity is necessary
- Vassil feels that Task should be required or at least should be "preferred"
- Will resume discussion next week
