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

Difference between revisions of "CMET Management by MnM"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents an [[:category:MnM Open Hot Topic|Open]] [[:category:MnM Hot Topic|MnM Hot Topic]], i.e. a methodology issue requiring a resolution from Modeling and Methodology.
+
This page documents an [[:category:MnM Hot Topic|MnM Hot Topic]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:MnM Hot Topic]][[Category:AboutCMETs]]
 
[[Category:MnM Hot Topic]][[Category:AboutCMETs]]
[[Category:MnM Open Hot Topic]]
+
{{MnM Closed Hot Topic}}
 
==Concerns==
 
==Concerns==
 
*Manage the CMET Identifier and Name Spaces for HL7 UV CMETs
 
*Manage the CMET Identifier and Name Spaces for HL7 UV CMETs

Revision as of 15:48, 11 June 2013

Concerns

  • Manage the CMET Identifier and Name Spaces for HL7 UV CMETs
    • Maintain CMET Master Spreadsheet - ok
    • Manage "root" of cmet names as (example) A_ObservationYadaYadaYada
      • Prefix is obvious
      • second element is the name determined by the root classCode
      • YadaYadaYada should be as generic as possible and represent the content
  • Manage the "attribution-level" names and definitions
    • Publish a pre-defined set as "preferrred" - if it matches your intentions, use it.
    • Review non-"universal" attributions to be sure they are
      1. Proper constraint on the "universal", if a "universal" exists
      2. Constraint patterns are appropriate to attribution level definition
  • Act as Coordinator
    • Assure that Naming is "consistent"
    • Needs strong Style Guides that are "testable"
    • Allow as much independence to the domains as possible
      • Have "managed" "UV" CMETs with domain identifiers from "parent" domain
      • Verify that "new" publishing leaves CMET "primary" content in domain directories and builds the "Common" stuff by "including" these
  • Revise and then Facilitate ANSI Registrations for releases

Bold text