This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Infrastructure and Messaging"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
The mission of the Infrastructure and Messaging TC (InM) is to provide the infrastructural support required in order for systems to exchange [[domain content]] as specified by HL7. | The mission of the Infrastructure and Messaging TC (InM) is to provide the infrastructural support required in order for systems to exchange [[domain content]] as specified by HL7. | ||
== Agendas/Minutes== | == Agendas/Minutes== | ||
| − | |||
| − | |||
[[20160112_orlando_agenda | Orlando Agenda]] | [[20160112_orlando_agenda | Orlando Agenda]] | ||
Revision as of 13:31, 11 January 2016
This is the main page of the Infrastructure and Messaging (InM) TC, formerly known as the Control Query (CQ) TC.
The mission of the Infrastructure and Messaging TC (InM) is to provide the infrastructural support required in order for systems to exchange domain content as specified by HL7.
Contents
Agendas/Minutes
Active Projects
- Chapter 2* issues in V2.8
- Abstract Transport Specification
- CCOW reaffirmation
- Shared Messages R3 Reaffirmation
- Master file-registry infrastructure reaffirmation
- Transmission Infrastructure reaffirmation
- DAF homepage
Committee Documents
These documents are open documents for editing by any interested party:
- Workitems: InM Workitem category
- INM Glossary Category:INM Glossary
- Wrappers R2
- Open ATS Issues
Scheduling proposal:InM Scheduling
The following are the open actions items for InM.
- All Action Items(In Dictionary format)
- INM Transmission and Transport Action Items (MCCI, ATS, Messaging Infrastructure)
- V2 Action Items and proposals
The following collaborative documents are edited by the InM co-chairs:\
Old Stuff waiting for re-organization
Other Documents
These documents are listed here for reference purposes:
