This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CTS2N - 17-April-12"
Jump to navigation
Jump to search
| Line 36: | Line 36: | ||
** Final document integrating the above | ** Final document integrating the above | ||
** … | ** … | ||
| + | |||
| + | * Update Old SFM Word doc to align with CP. Once editors are satisfied move to a new document (SFM boilerplate) and have Vocab WG review and approve. | ||
| + | |||
| + | Chair can Accept the alignment of the corret provide a document to vocabulary for approval | ||
| + | |||
| + | CS - moves | ||
| + | AE - 2nd | ||
| + | Motion carries unanimously | ||
| + | |||
| + | |||
Propose that vocabulary review and vote on our milestone deliverables. | Propose that vocabulary review and vote on our milestone deliverables. | ||
Revision as of 14:48, 17 April 2012
Contents
Minutes 17-Apr-2012
Roll Call and Agenda Check
- Ana Estelrich (AE)
- Russell Hamm (RH)
- Craig Stancl (CS)
- Kevin Peterson
- Brian Schweiller
- Senthil Nachimuthu (SN)
- Monica Harry (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?
Kevin - wh would control updates? How would we make/request changes?
RH - Russ will explore who will control changes.
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
- …
- Update Old SFM Word doc to align with CP. Once editors are satisfied move to a new document (SFM boilerplate) and have Vocab WG review and approve.
Chair can Accept the alignment of the corret provide a document to vocabulary for approval
CS - moves AE - 2nd Motion carries unanimously
Propose that vocabulary review and vote on our milestone deliverables.
