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

Difference between revisions of "List of Precepts Under Development"

From HL7Wiki
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
+
*Artifact governance
**SGB to produce a precept requiring that, in order to publish a specification, it has to be conformant to any harmonization patterns that HL7 has published
+
*Create precept regarding addressing identifier errors
**State Machine Alignment
+
*Bringing large projects into HL7
**How groups are to interact with Publishing, EST, Vocabulary, etc. WGs
 
**Engaging the implementer community in the consideration of changes as artifacts mature
 
 
**Engagement in large cross-organizational projects
 
**Engagement in large cross-organizational projects
**How management groups document, enforce, and manage the precepts regarding inter-WG participation in artifact creation
+
*SGB to produce a precept requiring that, in order to publish a specification, it has to be conformant to any harmonization patterns that HL7 has published
**Management groups must establish in writing a refinement of examples that adhere to the definition of substantive change that apply to their product family. Must monitor, audit, and measure conformance to the definition of substantive change.
+
*State Machine Alignment
**The addition of new tools (with EST)
+
*How groups are to interact with Publishing, EST, Vocabulary, etc. WGs
**Managing unresponsive parties in PSS approval process
+
*Engaging the implementer community in the consideration of changes as artifacts mature
**Vocabulary
+
*The addition of new tools (with EST)
**Training WGs in CDA methodology and management principles
+
*Vocabulary
**Vitality Assessment
+
*Vitality Assessment
 +
*Making sure that WGs involve those whose content domain they’re touching
 +
*A portion of a Normative standard being dropped to a lower level (STU) during the ballot process, and is that a substantive change?
 +
**One possible solution would be that these cases go to recirculation ballot.
 +
*Create precepts that require that it be articulated in the standards how the value sets specified within the standards respond to changes in regulation, licensing, time, etc.

Latest revision as of 15:11, 19 March 2019

  • Artifact governance
  • Create precept regarding addressing identifier errors
  • Bringing large projects into HL7
    • Engagement in large cross-organizational projects
  • SGB to produce a precept requiring that, in order to publish a specification, it has to be conformant to any harmonization patterns that HL7 has published
  • State Machine Alignment
  • How groups are to interact with Publishing, EST, Vocabulary, etc. WGs
  • Engaging the implementer community in the consideration of changes as artifacts mature
  • The addition of new tools (with EST)
  • Vocabulary
  • Vitality Assessment
  • Making sure that WGs involve those whose content domain they’re touching
  • A portion of a Normative standard being dropped to a lower level (STU) during the ballot process, and is that a substantive change?
    • One possible solution would be that these cases go to recirculation ballot.
  • Create precepts that require that it be articulated in the standards how the value sets specified within the standards respond to changes in regulation, licensing, time, etc.