This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Workflow Minutes CC 20150418"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
* Look at using DecisionSupportRule as being our "reuseable activity" | * Look at using DecisionSupportRule as being our "reuseable activity" | ||
* We will want to have the capability to express computable or descriptive variability on individual elements - this will probably be done as extensions. WGs will decide what extensions they need, but should align those extensions with how the equivalent is done in the Protocol resource | * We will want to have the capability to express computable or descriptive variability on individual elements - this will probably be done as extensions. WGs will decide what extensions they need, but should align those extensions with how the equivalent is done in the Protocol resource | ||
| + | ** These same computable & descriptive logic extensions would be relevant for use on orders as well where elements need to have dynamic/calculated values (e.g. dosage calculations, relative timings, etc.) | ||
==Composite Order== | ==Composite Order== | ||
Revision as of 18:11, 20 April 2016
FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)
Return to FHIR Workflow Minutes
Agenda
- Approve Minutes Prior Meeting on 04/11
Attendees
- Lloyd McKenzie (chair/scribe)
- Andrea Pitkus
- Bryn Rhodes
- Gary Dickinson
- Hans Buitendijk
- John Hatem
- Karl Holzer
- Lee Surprenant
- Michelle Miller
- Miranda Hoang
- Oliver Krauss
- Scott Robertson
- Viet Nguyen
- Jose Costa Teixeira
- Rob Hausam (joined after minutes)
- Robert Dieterle
Minutes
Motion to approve minutes of Apr. 11: Hans/Andrea: 11-0-2
Protocol discussion
Lloyd and Bryn talked about their discussions re: integrating Protocol and OrderSet
- Plan is to broaden OrderSet to encompass what Protocol does
- Refine how OrderSet defines activities to reflect what Protocol does, but allowing dynamic behavior by defining value of an attribute by an expression
- Look at using DecisionSupportRule as being our "reuseable activity"
- We will want to have the capability to express computable or descriptive variability on individual elements - this will probably be done as extensions. WGs will decide what extensions they need, but should align those extensions with how the equivalent is done in the Protocol resource
- These same computable & descriptive logic extensions would be relevant for use on orders as well where elements need to have dynamic/calculated values (e.g. dosage calculations, relative timings, etc.)
Composite Order
- Bob D. and others will look to identify use cases they feel can't be solved without having a distinct record for a "parent" order in a composite scenario
