Difference between revisions of "DECOR short intro"
| Line 17: | Line 17: | ||
<div class="vcard-header light-blue"><center>[[File:Web.svg|30px]][[File:Account-multiple-outline.svg|30px]]</center></div> | <div class="vcard-header light-blue"><center>[[File:Web.svg|30px]][[File:Account-multiple-outline.svg|30px]]</center></div> | ||
<div class="vcard-text"> | <div class="vcard-text"> | ||
| − | From | + | From the base requirements, the caregivers documented, terminologist can add the appropriate codes, associate caregiver concepts with coded concepts and create and maintain the value sets to be used. Typically also namespaces, identifiers, URIs and OIDs are assigned. |
</div> | </div> | ||
</div> | </div> | ||
Revision as of 15:49, 20 July 2020
DECOR (Data Elements, Codes, OIDs and Rules) is a methodology to capture the data needs of caregivers in terms of datasets and scenarios and use it to generate various artefacts: documentation, value sets, XML instance validation, generation and processing support, and test tools etc.
DECOR allows to iteratively improve recorded data and link together input from various experts with different background knowledge: caregivers, terminologist, modelers, analysts and interface/communication specialists.
  For caregivers, the tools mainly registers data elements and their collections as data sets with concepts, data types, allowable value ranges, identifications, codes, examples and business rules etc. In addition, use case specific Scenario's can be documented. |
  From the base requirements, the caregivers documented, terminologist can add the appropriate codes, associate caregiver concepts with coded concepts and create and maintain the value sets to be used. Typically also namespaces, identifiers, URIs and OIDs are assigned. |
 Modelers, analysts and interface / communication specialists add the technical representations as e.g. HL7 CDA templates, HL7 FHIR or IHE profiles. During that design phase and also in the following implementation and production phases the tool allows comprehensive validation and testing. |
 During development and production phases stakeholders and team members of the governance group are supported by an artefact-aware issue and reporting management that enables effective change management of the artefacts. |
The underlying DECOR data format is XML. The generation of HTML-, PDF- and Wiki-based documentation and XML-materials like validation and test environments is possible through a release and archive management function and transformations with stylesheets. The technical artefacts like templates and value sets can be used as input for test suites like IHE Gazelle ObjetcsChecker. Easy consistency checks across all artefacts can be achieved, CDA-based template definition can be verified to be standard conformant with the underlying CDA standard.
