This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20180328"
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== | ||
| − | *Approve [[FHIR | + | *Approve [[FHIR Workflow_Minutes_CC_20180326| Minutes Prior Meeting on 03/26]] |
==Attendees== | ==Attendees== | ||
*Lloyd McKenzie (chair/scribe) | *Lloyd McKenzie (chair/scribe) | ||
| − | * | + | *Nick Radov |
| + | *Reinhard Egelkraut | ||
| + | *Robert Lario | ||
==Minutes Approval== | ==Minutes Approval== | ||
| − | *Motion to approve [[FHIR | + | *Motion to approve [[FHIR Workflow_Minutes_CC_20180326| Minutes Prior Meeting on 03/26]]: Reinhard/Nick - 3-0-0 |
| − | == | + | ==Continued discussion with Robert Lario== |
| − | + | * Talked further about REST, Messaging and "Services" paradigms | |
| + | ** Our constraining of the use of REST to just create/read/update/delete doesn't necessarily align with general usage of the term | ||
| + | * Operation-based approach provides greater specificity about exactly what can be done and what elements are required but provides less out-of-the-box interoperability and requires more negotiation. | ||
| + | * Using Task or the 'actionable' tag is general purpose and requires little negotiation, but doesn't allow expression of what sorts of fulfillment are possible by a given system, what the input dependencies are, what systems will pay attention to fulfillment requests, etc. | ||
| + | * We need to have some discussion around capability statements and workflow | ||
==Adjournment== | ==Adjournment== | ||
| + | 3:03 Eastern | ||
Latest revision as of 15:00, 30 March 2018
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
- Approve Minutes Prior Meeting on 03/26
Attendees
- Lloyd McKenzie (chair/scribe)
- Nick Radov
- Reinhard Egelkraut
- Robert Lario
Minutes Approval
- Motion to approve Minutes Prior Meeting on 03/26: Reinhard/Nick - 3-0-0
Continued discussion with Robert Lario
- Talked further about REST, Messaging and "Services" paradigms
- Our constraining of the use of REST to just create/read/update/delete doesn't necessarily align with general usage of the term
- Operation-based approach provides greater specificity about exactly what can be done and what elements are required but provides less out-of-the-box interoperability and requires more negotiation.
- Using Task or the 'actionable' tag is general purpose and requires little negotiation, but doesn't allow expression of what sorts of fulfillment are possible by a given system, what the input dependencies are, what systems will pay attention to fulfillment requests, etc.
- We need to have some discussion around capability statements and workflow
Adjournment
3:03 Eastern
