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
(Created page with "= 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 P...")
 
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
= Minutes 17-Apr-2012=
 
= Minutes 17-Apr-2012=
  
== Roll Call and Agenda Check==
+
== Roll Call ==  
 
* Ana Estelrich (AE)
 
* Ana Estelrich (AE)
* Monica Harry (MH)
+
* Russell Hamm (RH)
 +
* Craig Stancl (CS)
 +
* Kevin Peterson
 +
* Brian Schweiller
 
* Senthil Nachimuthu (SN)
 
* Senthil Nachimuthu (SN)
* Russell Hamm (RH)
 
  
* Craig Stancl (regrets)
+
* Monica Harry (regrets)
* Kevin Peterson (regrets)
 
 
* Frank Oemig (regrets)
 
* Frank Oemig (regrets)
  
 +
 +
== Agenda Check==
 
* No additional agenda items
 
* No additional agenda items
 +
  
 
== Announcements ==
 
== 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
+
* 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?
 +
 
 +
 
 +
Kevin - Who would control updates?  How would we make/request changes?
  
 +
Action - Russ will explore who will control changes to cts2.org.
  
 
== Action Item Review ==
 
== Action Item Review ==
 +
# Russ will follow up with HL7 on how we make voting rules official.
 +
 +
Russ to write up the CTS 2N voting policy, and move to get Vocabulary approval on Thursday's main vocabulary call.  Policy will be one co-chair and simple majority with Vocabulary voting on major milestones.
 +
 +
== CTS 2 Milestones ==
 +
* Discuss deliverable milestones and dates for CTS 2. Potential milestones include:
 +
** A document outlining how the CTS 2 information and functional model in the SFM aligns 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
 +
** …
 +
 
*  
 
*  
  
== CTS 2 Voting Rules ==
+
Chair can Accept the alignment of the correct provide a document to vocabulary for approval
* 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 ==
+
'''Motion''' (CS): Update the original SFM Word document to align with the HL7 core principles of vocabulary.  Once editors are satisfied move to a new document (SFM boilerplate) and have Vocab WG review and approve.
* (AE) Functional requirement is not implemented in the PIM
+
AE - 2nd
** Verify with PIM authors on weather we are correct or not.
+
Motion carries unanimously
** 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.
 
  
  
  
== What Should CTS 2N Look Like ==
+
'''Motion''' (CS) : CTS 2 create a matrix that aligns the OMG PIM and HL7 SFM documenting what operatios are implemented (or not) in the PIM provide rationalization and description and location of that operation in  the PIM.  This document will be reviewed and voted on by the VOcabulary WG.
 +
Second: AE
 +
Motion carries unanimously
  
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.
 
  
 +
Propose that vocabulary review and vote on our milestone deliverables.
  
== Action items for Next Week ==
+
== Preliminary agenda 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
+
== Action Items ==
 +
* '''Russ''' will explore who will control changes to cts2.org.
 +
* Russ to write up voting policy
 +
* '''Craig''' to send OMG omissions list to list.

Latest revision as of 02:46, 24 April 2012

Minutes 17-Apr-2012

Roll Call

  • Ana Estelrich (AE)
  • Russell Hamm (RH)
  • Craig Stancl (CS)
  • Kevin Peterson
  • Brian Schweiller
  • Senthil Nachimuthu (SN)
  • Monica Harry (regrets)
  • Frank Oemig (regrets)


Agenda Check

  • 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?


Kevin - Who would control updates? How would we make/request changes?

Action - Russ will explore who will control changes to cts2.org.

Action Item Review

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

Russ to write up the CTS 2N voting policy, and move to get Vocabulary approval on Thursday's main vocabulary call. Policy will be one co-chair and simple majority with Vocabulary voting on major milestones.

CTS 2 Milestones

  • Discuss deliverable milestones and dates for CTS 2. Potential milestones include:
    • A document outlining how the CTS 2 information and functional model in the SFM aligns 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

Chair can Accept the alignment of the correct provide a document to vocabulary for approval

Motion (CS): Update the original SFM Word document to align with the HL7 core principles of vocabulary. Once editors are satisfied move to a new document (SFM boilerplate) and have Vocab WG review and approve. AE - 2nd Motion carries unanimously


Motion (CS) : CTS 2 create a matrix that aligns the OMG PIM and HL7 SFM documenting what operatios are implemented (or not) in the PIM provide rationalization and description and location of that operation in the PIM. This document will be reviewed and voted on by the VOcabulary WG. Second: AE Motion carries unanimously


Propose that vocabulary review and vote on our milestone deliverables.

Preliminary agenda items for next week

Action Items

  • Russ will explore who will control changes to cts2.org.
  • Russ to write up voting policy
  • Craig to send OMG omissions list to list.