Difference between revisions of "Consolidated CDA Templates Suggested Enhancements"
Bamarquard (talk | contribs) |
Bamarquard (talk | contribs) |
||
| Line 2: | Line 2: | ||
NOTE: Membership on this list bestows no special privileges. The list is just a convenient catalog of various comments received along the way. Each of these suggested enhancements will need use case backing, a formal proposal, etc before being considered for the Consolidated Templates DSTU. There is no requirement that an item be on this list to be considered for the Consolidated Templates DSTU. | NOTE: Membership on this list bestows no special privileges. The list is just a convenient catalog of various comments received along the way. Each of these suggested enhancements will need use case backing, a formal proposal, etc before being considered for the Consolidated Templates DSTU. There is no requirement that an item be on this list to be considered for the Consolidated Templates DSTU. | ||
| + | |||
| + | |||
| + | == Enhancement Process == | ||
| + | |||
| + | '''Requirements''' | ||
| + | 1. Ability to add new content, sections/entries/documents types, without requiring existing implementers to updates their system | ||
| + | 2. Regular update cycle, minimum of 12-months | ||
| + | 3. Clear versioning of Consolidation IG | ||
| + | 4. The Consolidation DSTU brought together multiple documents into one, and keeping them in one guide is preferred. | ||
| + | 5. SDWG will define guidance for how future DSTUs are added to Consolidation. | ||
| + | 6. SWDG will be the project sponsor when new documents are added to Consolidation | ||
| + | |||
| + | |||
| + | Potential Solutions based on Requirements above | ||
| + | 1. Updates and additions of SHOULD/MAY constraints through a ballot process without requiring templateId updates. | ||
| + | 2. Updates and additions of SHALL constraints will go through a template harmonization process and added at the periodic update. | ||
| + | 3. New document types will be balloted as a separate document and folded at the periodic update. | ||
Revision as of 14:12, 24 January 2012
Return to SDWG page.
NOTE: Membership on this list bestows no special privileges. The list is just a convenient catalog of various comments received along the way. Each of these suggested enhancements will need use case backing, a formal proposal, etc before being considered for the Consolidated Templates DSTU. There is no requirement that an item be on this list to be considered for the Consolidated Templates DSTU.
Enhancement Process
Requirements 1. Ability to add new content, sections/entries/documents types, without requiring existing implementers to updates their system 2. Regular update cycle, minimum of 12-months 3. Clear versioning of Consolidation IG 4. The Consolidation DSTU brought together multiple documents into one, and keeping them in one guide is preferred. 5. SDWG will define guidance for how future DSTUs are added to Consolidation. 6. SWDG will be the project sponsor when new documents are added to Consolidation
Potential Solutions based on Requirements above
1. Updates and additions of SHOULD/MAY constraints through a ballot process without requiring templateId updates.
2. Updates and additions of SHALL constraints will go through a template harmonization process and added at the periodic update.
3. New document types will be balloted as a separate document and folded at the periodic update.
