This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20160224"
Jump to navigation
Jump to search
| Line 38: | Line 38: | ||
Discussed difference between "received" and "accepted". Relevant when there may be a delay in "taking ownership" of a task vs. committing to do it. "requested" could have multiple assignees, but all other statuses, task must have a single specific performer. Once rejected, placer must create a new task to solicit alternate fillers. | Discussed difference between "received" and "accepted". Relevant when there may be a delay in "taking ownership" of a task vs. committing to do it. "requested" could have multiple assignees, but all other statuses, task must have a single specific performer. Once rejected, placer must create a new task to solicit alternate fillers. | ||
| + | |||
| + | ==Workflow use-case== | ||
| + | Updated Lab scenario with additional details. | ||
| + | See: [http://wiki.hl7.org/images/4/49/Composite_order_example.docx] | ||
==Adjournment== | ==Adjournment== | ||
Latest revision as of 19:09, 29 February 2016
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
- Approve Minutes Prior Meeting on 02/22
Attendees
- Lloyd McKenzie (chair/scribe)
- Jaspreet Birk
- John Hatem
- Jose Costa Teixeira
- Marla Albitz
- Michelle Miller
- Chethan Makonahalli
- Gary Dickinson
- Hans Buitendijk
- Julia Chan
- Kevin O'Donnell
- Rob Hausam
- Josh Mandel
Minutes
Motion to approve Feb 22 minutes: John/Jose 9-0-2
Statuses
Discussed "task" statuses. Agreed on:
- requested
- received
- rejected
- accepted
- in-progress
- failed
- completed
Also, need to have "business" states that can differentiate different "degrees" of "accepted", "in-progress", etc.
Discussed difference between "received" and "accepted". Relevant when there may be a delay in "taking ownership" of a task vs. committing to do it. "requested" could have multiple assignees, but all other statuses, task must have a single specific performer. Once rejected, placer must create a new task to solicit alternate fillers.
Workflow use-case
Updated Lab scenario with additional details. See: [1]
