CTS2N - 14-Feb-12

Minutes 14-Feb-2012

Roll Call and Agenda Check

• Ana Estelrich (AE)
• Jim Case
• Ken Rubin (KR)
• Monica Harry
• Senthil Nachimuthu (SN)
• Craig Stancl
• Kevin Petersen
• Russell Hamm
• Frank Oemig
• Jan Wittenbur

Announcements

• Call in information - HL7 no longer provides toll free calling. Previous agenda was incorrect and has been corrected.

Action Item Review

• Russ to post wiki information for minutes - complete
• Discuss with the OMG FTF to have a vote to make the OMG documents public and available on CTS 2 Normative wiki. - Complete
• Ana to ping Frank / Berndt on their CTS 2 efforts.

Infrastructure / Asset Review

• Wiki
  • [http://wiki.hl7.org/index.php?title=Common_Terminology_Services_-_Release_2_%28Normative%29]
  • To be used for managing project related assets, meeting minutes, etc.
• Project Documentation (SFM / PIM)
  • HL7 SFM located here: * [HL7's Common Terminology Services - Release 2 Service Functional Model (CTS 2 SFM)]
  • OMG PIM artifacts located here: [Documents Associated with Common Terminology Services 2 (CTS2) 1.0 - Beta 1]
  • [Platform Specific Model]
  • [CTS 2 Development Framework]
• Functional Requirements Mapping
  • To be maintained in a Google Docs spreadsheet
• Normative SFM
  • To be maintained in a Google Docs document

Discussion

Frank Oemig outlined the work going on in Germany and Austria pertaining to CTS 2 development from the SFM. Frank called out two specific areas of the SFM that require further discussion/enhancement in the normative SFM.

1. Conformance is missing from the SFM. Both the SFM and the PIM allow for piecemeal development of CTS 2 services. While this is a strength, the HL7 SFM should establish a conformance profile that outlines the functionality for a

Action Items

• Russ to investigate and establish mapping document and SFM document in Google docs.

Items for Next Agenda

HL7 Conformance Profile

• What should it look like (messaging / browsing / mapping)
• Required functionality