This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CTS2N - 17-April-12"

From HL7Wiki
Jump to navigation Jump to search
Line 18: Line 18:
  
 
== Action Item Review ==
 
== Action Item Review ==
−
*
+
# Russ will follow up with HL7 on how we make voting rules official.
−
 
 
−
== CTS 2 Voting Rules ==
 
−
* By default I believe we adopt the Vocabulary WG calls.  We will unlikely have 2 chairs on CTS 2 calls. 
 
−
*(RH) Propose voting rules of one Vocabulary chair and three participants for binding votes.
 
−
** Aknowledged and agreed by all three members
 
−
** Russ will follow up with HL7 on how we make this official.
 
−
 
 
−
== Work Items Review ==
 
−
* (AE) Functional requirement is not implemented in the PIM
 
−
** Verify with PIM authors on weather we are correct or not.
 
−
** Then what?
 
−
*** Exclude the requirement all together?
 
−
*** Add a section of the document that talks to why each requirement was not included in the PIM
 
−
*** Discuss the use of CTS 2 within the broader context of a terminology enabled application
 
−
* Ana has began making corrections to the Word version of the DSTU.
 
−
 
 
  
 +
== CTS 2 Milestones ==
 +
* Discuss deliverable milestones and dates for CTS 2. Potential milestones include:
 +
** Document outlining CTS 2 information and functional model alignment with HL7 Core Principles of vocabulary
 +
** PIM->SFM matrix alignment (validate what functionality is/is not present in the PIM based on the SFM requirements.  Document the rationalization of the design decisions made in the PIM
 +
** HL7 terminology model (MIF based)
 +
** Conformance profile for HL7 CTS 2
 +
** Document from implementers outlining changes to the SFM functional requirements based on user experience
 +
** Final document integrating the above
 +
** …
  
−
== What Should CTS 2N Look Like ==
 
  
−
This is a discussion on what the end goal of CTS 2N should be.  What should the end product look like?  What should it include/not include. What should the normative CTS 2 look to accomplish.
 
−
 
−
* What functionalities do I require as an implementer to say I am CTS 2 compliant?
 
−
** This speaks the need for a '''HL7 CTS 2 conformance profile'''.
 
−
* CTS 2 should be aligned with HL7 core principles of vocabulary
 
−
* CTS 2 could include appendices outlining different implementation/representation choices for the SFM (OMG v PHAST)
 
−
* Should CTS 2N include or reference an HL7 Terminology Model (MIF)?
 
−
** How to include model updates identified by PHAST
 
−
* Should CTS 2N provide rational to the decisions made in the PIM.
 
  
  
 
== Action items for Next Week ==
 
== Action items for Next Week ==
−
# Russ will follow up with HL7 on how we make voting rules official.
 
−
# Ana will email to list the mapping spreadsheets
 

Revision as of 23:19, 16 April 2012

Minutes 17-Apr-2012

Roll Call and Agenda Check

  • Ana Estelrich (AE)
  • Monica Harry (MH)
  • Senthil Nachimuthu (SN)
  • Russell Hamm (RH)
  • Craig Stancl (regrets)
  • Kevin Peterson (regrets)
  • Frank Oemig (regrets)
  • No additional agenda items

Announcements

  • RH - cts2.org currently redirects to apelon.com. This is being reworked to be more inclusive. One item being considered is a launcher page that would provide links to the various cts 2 activities such as the NOrmative work in HL7, the OMG PIM, implementation guides, the development framework, etc. What other options should we consider for the cts2.org page?


Action Item Review

  1. Russ will follow up with HL7 on how we make voting rules official.

CTS 2 Milestones

  • Discuss deliverable milestones and dates for CTS 2. Potential milestones include:
    • Document outlining CTS 2 information and functional model alignment with HL7 Core Principles of vocabulary
    • PIM->SFM matrix alignment (validate what functionality is/is not present in the PIM based on the SFM requirements. Document the rationalization of the design decisions made in the PIM
    • HL7 terminology model (MIF based)
    • Conformance profile for HL7 CTS 2
    • Document from implementers outlining changes to the SFM functional requirements based on user experience
    • Final document integrating the above
    • …



Action items for Next Week

Retrieved from "https://wiki.hl7.org/w/index.php?title=CTS2N_-_17-April-12&oldid=60867"