This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20151216"
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) |
| − | + | *Keith Boone | |
| + | *Eric Haas | ||
| + | *??? | ||
| + | |||
| + | ==Mapping between Order/ActionRequest and Task== | ||
| + | * Discussed the relationship between Keith's proposed Task resource and the Order/ActionRequest resource | ||
| + | |||
| + | :'''Task''' -> '''Order/ActionRequest''' | ||
| + | :identifier -> identifier | ||
| + | :type -> Order.code (proposed) | ||
| + | :performerType -> | ||
| + | :priority -> Consider adding to Order, but probably an extension. (The base order has priority, but the fulfillment request/state change doesn't often) | ||
| + | :status -> Deferred to discussion about single Task resource vs. dual Order/OrderResponse resource approach | ||
| + | :subject -> subject | ||
| + | :definition -> extension | ||
| + | :created -> date | ||
| + | :lastModified -> Part of meta | ||
| + | :owner -> target | ||
| + | :creator -> source | ||
| + | :manager -> extension, at least for now | ||
| + | :input -> detail | ||
| + | :output -> OrderResponse.fulfillment | ||
| − | |||
| − | |||
==Agenda Item 2== | ==Agenda Item 2== | ||
Revision as of 18:36, 4 January 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)
- Keith Boone
- Eric Haas
- ???
Mapping between Order/ActionRequest and Task
- Discussed the relationship between Keith's proposed Task resource and the Order/ActionRequest resource
- Task -> Order/ActionRequest
- identifier -> identifier
- type -> Order.code (proposed)
- performerType ->
- priority -> Consider adding to Order, but probably an extension. (The base order has priority, but the fulfillment request/state change doesn't often)
- status -> Deferred to discussion about single Task resource vs. dual Order/OrderResponse resource approach
- subject -> subject
- definition -> extension
- created -> date
- lastModified -> Part of meta
- owner -> target
- creator -> source
- manager -> extension, at least for now
- input -> detail
- output -> OrderResponse.fulfillment
Agenda Item 2
Goes here
