This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Composite Order"

From HL7Wiki
Jump to navigation Jump to search
Line 25: Line 25:
  
 
==Characteristics of a Composite Order==
 
==Characteristics of a Composite Order==
The current design thinking for Composite Order is to move from an entirely constraint-based approach to a building-blocks approach.  Meaning we're moving from a big DMIM, from which all RMIMs are properly derived to an approach where the DMIM is a representation of the RIM and templates are applied to define constraints.
+
The current design thinking for Composite Order is to move from an entirely constraint-based approach to a building-blocks approach; a move which we believe aligns with the SAIF principles and emerging HL7 Architecture.  Meaning we're moving from a big DMIM which represents the collective knowledge for a topic or subject area (Laboratory, Pharmacy, etc.)from which all RMIMs in that business topic are properly derived, to an approach where the DMIM is more general (realistically a representation of the RIM).  Then RMIMs are templates which are applied to define constraints.  One of the new key principles of this approach is that successive templates are applied to the DMIM, each which adds business context.
 
*with order constraints? (some like this approach)
 
*with order constraints? (some like this approach)
 
*without order constraints? (others like this approach)
 
*without order constraints? (others like this approach)
Line 31: Line 31:
 
What does it mean to use the RIM or a barely constrained version of the RIM as the composite order as a DMIM?
 
What does it mean to use the RIM or a barely constrained version of the RIM as the composite order as a DMIM?
  
OO asserts that Composite Order is a template.  In this case, we define template as a set of definitions which are constraints on the parent model for the core data.  However, the 'edge' of the template (scope) of the template at this level is up for discussion.  In composite order template, do we use any CMETs?  What is the edge or scope (can that be implied by the need for a CMET)?
+
OO asserts that Composite Order is a high-level template.  In this case, we define template as a set of definitions which are constraints on the parent model for the core data.  However, the 'edge' of the template (scope) of the template at this level is up for discussion.  In composite order template, do we use any CMETs?  What is the edge or scope (can that be implied by the need for a CMET)?   Specifically the composite order template is a common set of classes, common to all requests for healthcare services.  Specialized classes are not included in this template; and subject areas are expected to create specialized, topic and business-specific templates which define exact information content and constraints for a specific triggering action.
  
 
For example, there is a DMIM model for common product model.  CPM is then constrained and used by Pharmacy, for example.  So for composite order, do we 'reference' the CPM? do we put in a CPM 'stub'?
 
For example, there is a DMIM model for common product model.  CPM is then constrained and used by Pharmacy, for example.  So for composite order, do we 'reference' the CPM? do we put in a CPM 'stub'?

Revision as of 19:28, 16 September 2010

Back to Orders & Observations WG main page

Back to OO Projects page

Scope of Composite Order

The Composite Order topic includes the ability to order multiple basic healthcare services in one message; the disciplines included are request for lab services, diagnostic imaging services, and pharmacy services. This topic covers all interactions related to requesting single or combinations of healthcare services.

Note that the Composite Order project includes development of the SAIF behavioral model components. BF Alpha Project

Leadership

Co-Chair: Patrick Loyd; 415-209-0544, patrick.e.loyd@gmail.com

Project Facilitator: Patrick Loyd

Conference Calls and Minutes

Dates: Meets w/regularly scheduled OO conference calls. Weekly on Thursdays.

Time: 13:00 - 14:00 EST

Phone Number: +1 (770) 657 9270

Participant Passcode: 653212

Characteristics of a Composite Order

The current design thinking for Composite Order is to move from an entirely constraint-based approach to a building-blocks approach; a move which we believe aligns with the SAIF principles and emerging HL7 Architecture. Meaning we're moving from a big DMIM which represents the collective knowledge for a topic or subject area (Laboratory, Pharmacy, etc.)from which all RMIMs in that business topic are properly derived, to an approach where the DMIM is more general (realistically a representation of the RIM). Then RMIMs are templates which are applied to define constraints. One of the new key principles of this approach is that successive templates are applied to the DMIM, each which adds business context.

  • with order constraints? (some like this approach)
  • without order constraints? (others like this approach)

What does it mean to use the RIM or a barely constrained version of the RIM as the composite order as a DMIM?

OO asserts that Composite Order is a high-level template. In this case, we define template as a set of definitions which are constraints on the parent model for the core data. However, the 'edge' of the template (scope) of the template at this level is up for discussion. In composite order template, do we use any CMETs? What is the edge or scope (can that be implied by the need for a CMET)? Specifically the composite order template is a common set of classes, common to all requests for healthcare services. Specialized classes are not included in this template; and subject areas are expected to create specialized, topic and business-specific templates which define exact information content and constraints for a specific triggering action.

For example, there is a DMIM model for common product model. CPM is then constrained and used by Pharmacy, for example. So for composite order, do we 'reference' the CPM? do we put in a CPM 'stub'?

Further to this approach, the domain-specific model/template is then used to specify and define the model exactly for that domain's usage. The domain-specific model is a properly constraint on those higher-level templates as 'joined' in a large logical model (elaborate the stubs or references).

Documentation

Deliverables

Links

Open Composite Order Vocab Items