Architectural choices: One composition archetype per document type, or not?

Bakke, Silje Ljosland silje.ljosland.bakke at nasjonalikt.no
Thu Feb 11 09:17:04 EST 2016


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, RN
Coordinator, National Editorial Board for Archetypes
National ICT Norway
Tel. +47 40203298
Web: http://arketyper.no<http://arketyper.no/> / Twitter: @arketyper_no<https://twitter.com/arketyper_no>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20160211/0815317e/attachment-0002.html>


More information about the openEHR-clinical mailing list