Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Mission

The mission of the Infrastructure and Messaging Work Group (InM) is to provide the infrastructural support required in order for systems to exchange domain content as specified by HL7.

 Charter

Work Products and Contributions to HL7 Processes

The Infrastructure and Messaging work group will develop specifications using the principles and language of the SAIF CD and the restrictions and specializations of the HL7 SAIF IG to ensure traceability from Conceptual to Logical to Implementable specifications.

For HL7 Version 2 the InM Work Group is responsible for the ongoing maintenance and support of the normative HL7 Version 2 Query(chapter 2), Data Types(chapter 2a),Tables(Chapter 2c), Query(chapter 5), Master Files(Chapter 8) and Application Management(chapter 14). The InM Work Group will only accept changes (including additions) to the HL7 Version 2 materials if they meet the following criteria:

  •   The reason for the change needs to be either a documented regulatory requirement or a harmonization requirement with HL7 Version 2 material created by other committees.
  •   All change proposals need to be accompanied by an analysis of their relationship with, and impact on, comparable functionality in HL7 Version 3.

For HL7 Version 3 the InM Work Group will be responsible for the creation and maintenance of normative standards in the following areas:

  •   Transmission and Transport covers the MCCI Transmission Wrapper, the Abstract Transport Specification, , as well as the transmission interaction patterns (e.g. use of commit acks, Message Adapter rejects)
  •   Predefined Infrastructural Models covers the following areas:  
    •     Trigger Event Control Act wrapper templates (MCAI Generic Control Acts, MFMI Registries/Master Files, QUQI Queries) including application interaction patterns (application responses, query responses, conversations)
  •   Commonly used Message Types (COMT Shared Messages) and related application interaction patterns

For Clinical Context Object Workgroup (CCOW)

  •   InM will maintain and extend the standards as requirements dictate.

Former Responsibilities

  •   Implementable Technology Specifications (e.g. XML, UML) is now the responsibility of the Implementable Technology Specifications(ITS) work group.
  •   Abstract Data Types. Covers the technical quality of the data type definitions and ensuring their utility across all Work Groups is now the responsibility of the Modeling and Methodology(MnM) work group

Formal Relationships With Other HL7 Groups

InM in association with Conformance and Guidance for Implementation and Testing work group  and Vocabulary is the HL7 Version 2 Methodology group.

 Space Organization:

InM Decision Log:  A page listing decisions and their status.

InM Projects: A page listing the InM projects .

InM Meeting notes: Space for the agendas. logistics, etc.

 

 

Blog stream

InM has adopted Confluence/JIRA as an active work group.  We will be doing Agendas, Minutes and PSS's online, as well as using JIRA for tracking.

  • No labels