This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20180326"
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_20180319| Minutes Prior Meeting on 03/19]] |
==Attendees== | ==Attendees== | ||
*Lloyd McKenzie (chair/scribe) | *Lloyd McKenzie (chair/scribe) | ||
| − | * | + | *Jeff Danford |
| + | *John Moehrke | ||
| + | *Jose Costa Teixeira | ||
| + | *Robert Lario | ||
| + | *John Hatem | ||
==Minutes Approval== | ==Minutes Approval== | ||
| − | *Motion to approve [[FHIR | + | *Motion to approve [[FHIR Workflow_Minutes_CC_20180319| Minutes Prior Meeting on 03/19]] - Jose/Jeff: 5-0-0 |
| − | == | + | ==Services workflow== |
| − | + | * Lloyd presented an overview of what the workflow project has documented around workflow so far and what we're looking for in terms of "services" documentation | |
| + | *Robert shared two presentations on work by the OMG, primarily relating to representation of workflow protocols | ||
| + | * Lloyd shared that the workflow project is currently looking for guidance on the use of services to initiate/manage workflows, not to define them (as that's covered by PlanDefinition) | ||
| + | **REST – Creating/Updating/Deleting – HTTP only: | ||
| + | ***POST a ‘request’ resource tagged as “actionable” | ||
| + | ***POST a ‘TASK’ resource | ||
| + | **Messaging – Firing events and passing associated data. Use a FHIR Message with MessageHeader, etc. | ||
| + | ***Message with event of “please fulfill” pointing to the request resource | ||
| + | ***Task may or may not be involved | ||
| + | **Services – Make function calls/invoke operations (could be SOAP, HTTP, SMTP, etc.) | ||
| + | ***Invoke operation saying “please fulfill”, passing reference to request as a parameter and possibly other information (e.g. timeframe, etc.) | ||
==Adjournment== | ==Adjournment== | ||
| + | 3:03 Eastern | ||
Latest revision as of 02:29, 27 March 2018
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
- Approve Minutes Prior Meeting on 03/19
Attendees
- Lloyd McKenzie (chair/scribe)
- Jeff Danford
- John Moehrke
- Jose Costa Teixeira
- Robert Lario
- John Hatem
Minutes Approval
- Motion to approve Minutes Prior Meeting on 03/19 - Jose/Jeff: 5-0-0
Services workflow
- Lloyd presented an overview of what the workflow project has documented around workflow so far and what we're looking for in terms of "services" documentation
- Robert shared two presentations on work by the OMG, primarily relating to representation of workflow protocols
- Lloyd shared that the workflow project is currently looking for guidance on the use of services to initiate/manage workflows, not to define them (as that's covered by PlanDefinition)
- REST – Creating/Updating/Deleting – HTTP only:
- POST a ‘request’ resource tagged as “actionable”
- POST a ‘TASK’ resource
- Messaging – Firing events and passing associated data. Use a FHIR Message with MessageHeader, etc.
- Message with event of “please fulfill” pointing to the request resource
- Task may or may not be involved
- Services – Make function calls/invoke operations (could be SOAP, HTTP, SMTP, etc.)
- Invoke operation saying “please fulfill”, passing reference to request as a parameter and possibly other information (e.g. timeframe, etc.)
- REST – Creating/Updating/Deleting – HTTP only:
Adjournment
3:03 Eastern
