DAM vs DCM

return to: Patient Care further to: Detailed Clinical Models further to: Detailed Clinical Model instance construction

DAM vs DCM

This diagram illustrates the relationship between a Domain Analysis Model or DAM, as currently developed in the HL7 space and the Detailed Clinical Model or DCM. Both a DAM and a DCM are not created using HL7 methodology, but more generic health informatics modeling approaches. A DAM usually covers a whole clinical domain, for instance TB care, Cardiology, Emergency and so on. At a particular level a DAM remains generic, where detailed clinical data are expected to be expressed in another format. DCM steps in that space: the nitty gritty details. See the examples how detailed level we are working on with a DCM. So a DCM can be seen as a leaf node of a DAM. In addition that would apply also for the leaf node specification in the EHR profile.

When a DCM is available as an abstract specification of a clinical concept, its data-elements and specification and the relationships, it can be transformed into any kind of technological formalism. We do have several examples in the Care Provision Care Structures Topic where these reside as a R-MIM roll out of Care Statement / Clinical Statement. In the Assessment Scale Topic of Care Provision, several tables with data - element specifications and code bindings are illustrated, based on the work of Frank Oemig in Germany.

Finally, as illustrated in the picture DCM can be transformed into HL7 v3 templates as soon as these start becoming existent. Another formalism currently used for implementation of a DCM is the CEN/ISO 13606-2 archetype (as in ADL 1.2), or an OpenEHR archetype (as in ADL 1.4). Work is ongoing on the appropriate transformations.