This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">
Difference between revisions of "Requirements-Dynamic Model"
From HL7Wiki
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
3.How a receiving system knows when it has to send a particular type of response message(s) - (receiver responsibilities). | 3.How a receiving system knows when it has to send a particular type of response message(s) - (receiver responsibilities). | ||
| − | === | + | ==Requirements== |
| + | ===Dynamic Model=== | ||
{| border="2" cellspacing="0" cellpadding="3" width="600" | {| border="2" cellspacing="0" cellpadding="3" width="600" | ||
| '''Requirement''' | | '''Requirement''' | ||
Revision as of 21:59, 27 October 2009
This page documents one or more V3 Methodology Requirements
Contents
Description
The HL7 methodology includes two parts needed for communication pf information between systems, the static model (content itself and any wrappers) and the dynamic model (what is the receiver supposed to do with the information that has been communicated). This section seeks to briefly describe the dynamic model and to thoroughly document the dynamic model requirements for MIF.
The core of the HL7 dynamic model is the interaction. A formal definition from HL7:
A unique association between a specific message type (static model or document), a particular trigger event that initiates or "triggers" the transfer, and the Receiver Responsibilities (in terms of response interactions) associated with the receipt of the Interaction.
A single Interaction explicitly answers the questions: 1.What the particular message type is (static model which may be a document, a external addressing (transport) wrapper, and an 'action' wrapper. 2.What caused the message to be sent (triggering event) 3.What is expected of the receiving system (trigger event) 3.How a receiving system knows when it has to send a particular type of response message(s) - (receiver responsibilities).
Requirements
Dynamic Model
| Requirement | HL7 requires a structure for the dynamic model components. The primary structure is the interaction (described above). |
| Rationale | A formal structure is needed to produce formalized, harmonized standards. |
| MIF |
|
Trigger Events
| Requirement | Each interaction must have a trigger event. HL7 needs to be able to define the 'real world' occurrences that result in a need for information to be exchanged |
| Rationale | The trigger events must be able to be precisely referenced when creating interactions. The trigger event is the reason for communicating information. Part of interoperability is not only what information will get shared but also the circumstances where it will be shared. A system that does not share the appropriate information at the correct time will not achieve interoperability. |
| MIF |
|
| Requirement | Each trigger event must have a unique name |
| Rationale | The trigger events must be able to be precisely referenced when creating interactions. The trigger event is the reason for communicating information. |
| MIF |
|
| Requirement | Each trigger event must include a type. |
| Rationale | The trigger event types communiate the 'pattern' expected as far as receiver responsibilities. For example, and interaction-based trigger event is 'kicked off' when a triggering interaction is communicated. |
| Methodology | There are three types:
|
| MIF |
|
| Requirement | EnvironmentalOccurrence may have associated text. |
| Rationale | Describes the nature of the environmental occurrence (e.g. user action) |
| MIF |
|
| Requirement | EnvironmentalOccurrence may have a related state transition. |
| Rationale | Describes the state transition related to the environmental occurrence. A frequent example is when a user requests info to be posted to a patient's EHR (related state transition is to 'complete' an observation) and record it or to request diagnostic testing (related state transition is to 'activate' an order). |
| MIF |
|
| Requirement | State-based trigger events must reference the model being acted upon. |
| Rationale | Required to know which information model to update. |
| MIF |
|
Static Model References
| Requirement | Structured documents have a document definition (static model) |
| Rationale | Documents the primary payload model as well as any parameterized stubs within the model. |
| MIF |
|
Interations
| Requirement | Each interaction must have a unique name |
| Rationale | The interactions must be able to be precisely referenced esp. as part of receiver responsibilities. |
| MIF |
|
| Requirement | Each interaction must include one or more static models. There are use cases where only the transport wrapper, and/or transport and control act wrapper are communicated without a 'payload' (meaning a static model or document). |
| Rationale | The interactions must be able to be precisely referenced esp. as part of receiver responsibilities. Also, the receiving system needs to kn ow |
| MIF |
|
| Requirement | Each interaction may include one or more receiver responsibilities |
| Rationale | Frequently in response to an interaction, one or more 'response' interactions are triggered. There can be multiple responses. |
| MIF |
|
| Requirement | Each interaction may include one or more sending application and receiving application. |
| Rationale | ?. |
| MIF |
|
| Requirement | Each interaction may have an interaction type. |
| Rationale | Synonymous with trigger event types. |
| MIF |
|
| Requirement | Interactions have to be able to bind to a message model or a document as the payload. |
| Rationale | There are two 'types' of static model content at HL7. RMIMs which represent workflow-type communications and Documents which represent point-in-time information. |
| MIF |
|
| Requirement | Interactions may include a use type. |
| Rationale | Identifies the type of content represented by the model when entered from this entry point. The contentType determines whether the model is legitimate content for a classStub from another model. |
| MIF |
|
| Requirement | A static model may be a choice of payload models |
| Rationale | In some models, the payload is actually a choice of models. Used in models which bring in harmonized and/or summary data. |
| MIF |
|
| Requirement | For each query interaction, an additional binding to the parameter list is required. Note this includes query requests as well as query responses. |
| Rationale | The parameter list is required for both requests and responses. |
| MIF |
|
Receiver Responsibilities
| Requirement | Each receiver responsibility must have a reason. |
| Rationale | Indicates the conditions under which this receiver responsibility should be chosen. Should be mutually exclusive with the conditions of all other receiver responsibilities for this interaction. Also, the combined reasons for all receiver responsibilities should be complete. I.e. There should be no circumstance that doesn't fit into the reason of one and one receiver responsibility. |
| MIF |
|
| Requirement | A receiver responsibility may have one or more 'response' interactions. |
| Rationale | Supports acknowledgements as well as query responses. |
| MIF |
|
| Requirement | A receiver responsibility may have one or more 'response' trigger events. |
| Rationale | Indicates that the specified trigger event should be fired, along with any interactions associated with that trigger event and supported by any of the receiving system's application roles. |
| MIF |
|
Application Roles
| Requirement | Each application role must have a unique name |
| Rationale | The sending and receiving application role must be able to be precisely referenced when creating interactions. |
| MIF |
|
| Requirement | Each application role may have related application roles. |
| Rationale | Used to build composites. |
| MIF |
|
| Requirement | Each application role may be either or both sending interactions and/or receiving interactions. |
| Rationale | Application role is about the functional capability. Need to document for each role when the application expects to receiving information and act; or sends information. |
| MIF |
|
| Requirement | Each application role may either create or consume a document. |
| Rationale | Application roles need to deal with documents as well as other static models. |
| MIF |
|
| Requirement | Interactions, Trigger Events, Application Roles and Structured Documents may have a number of different types of annotations |
| Rationale | See rationales for individual annotations types |
| Implementation |
Future Requirements (not complete)
Note that HL7 is currently re-developing and replacing the current dynamic model methodolgy. Below are SOME of the requirements. Requirements are still being determined and documented as part of the HL7 Enterprise Architecture Framework Alpha implementation projects.
| Future Requirement | Communicate conformance of receiver responsibilities. It is necessary to know which receiver responsibilities must happen (mandatory), should happen (required), may happen (optional), and must not happen (usually based on a previous elaboration of a receiver responsibility). |
| Rationale | It is necessary to know which receiver responsibilities must happen (mandatory), should happen (required), may happen (optional), and must not happen (usually based on a previous elaboration of a receiver responsibility). |
| MIF |
|
