| Table of Contents |
|---|
Date
31 Oct 7 Nov 2019
Previous Meeting - Next Meeting
Agenda
Item / Topic | Presenter | Description |
|---|---|---|
| Discuss requirements of Order Set | Stephen White (Unlicensed) | Look at options and vote on approach |
Participants
Stephen White (Unlicensed); Keith Butler; @Marc Sainvil; Lloyd Dugan; @Jane Shellum; Keith Salzman; Robert Lario; Claude Nanjo
Goals
List goals for this meeting (e.g., Set design priorities for FY19):
- come up with an approach for handling the data requirements for Order Sets (and Questionnaires)
Notes (raw)
We reviewed the example we obtained for a Cardiology Order Set. The PlanDefinition of the Order Set was translated into BPM+ elements.
We discussed 2 different ways to include Order Set specific data into BPM+ data elements:
- Use Constraint mechanisms to show what the real-time data should be (see figure)
- Attach XML files to a Data Item with appropriate data values
The constraint approach builds the OrderSet info into the model, but it doesn't provide the capability of actually executing the a Process, Case, or Decision for the OrderSet. But it does provide direct modeling definition of the OrderSet data. We've been calling this data as being a "Prototype" of the generic data types (for a Medication Request, e.g.).
The attached file approach provides a more indirect method of including the OrderSet info into the model, but it does provide the capability for execution. The file would be available (and required) at runtime.
The same file would also be required for the constraint method. Thus, the OrderSet info would be created twice for the OrderSet method.
We didn't finish the discussion and will continue next week.
Chat Log
There was nothing in the chat this time.
...