Architectural choices: One composition archetype per document type, or not?
pazospablo at hotmail.com
Thu Feb 11 12:09:11 EST 2016
I think it is good to reuse a generic composition from many templates.
For querying, in that case, you can use the template id instead of the archetype id, since the template id is also part of the ARCHETYPED data. See http://openehr.org/releases/1.0.2/architecture/rm/common_im.pdf page 13.
Eng. Pablo Pazos Gutiérrez
Subject: Architectural choices: One composition archetype per document type, or not?
From: silje.ljosland.bakke at nasjonalikt.no
To: openehr-clinical at lists.openehr.org
Date: Thu, 11 Feb 2016 15:17:04 +0100
When implementing an openEHR based system for a large hospital, there will be hundreds if not thousands of document types. Examples of these are admission notes for different departments and specialties, outpatient notes, nursing documentation, check lists, discharge summaries, etc ad infinitum. Each of these could either have its own COMPOSITION archetype, or they could reuse generic compositions but have a separate template for each document type. What’s the smart architectural choice to make here; 1-1 document type – COMPOSITION, or reuse of generic COMPOSITIONs in specific templates? Why? How can you query a specific document type if it doesn’t have its own COMPOSITION? Kind regards,
Silje Ljosland Bakke Information Architect, RNCoordinator, National Editorial Board for Archetypes
National ICT NorwayTel. +47 40203298Web: http://arketyper.no / Twitter: @arketyper_no
openEHR-clinical mailing list
openEHR-clinical at lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openEHR-clinical