I have certainly built templates where there is no expected content, only additional other_contecxt and I can imagine situations where any/all data could be carried by Composition RM attributes e.g in feeder_audit, so I can't see a good reason for enforcing content.
Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation [email protected] Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On Thu, 26 Jul 2018 at 09:59, GF <[email protected]> wrote: > In the archetype the amount of constraints must be minimal. > In the Template the amount of constraints must be optimal (maximal?) > > Archetypes are generic patterns. > Templates are specific patterns. > > Generic meaning to be used in all systems at all points in time. > Specific meaning to be used in a jurisdiction at a point in time. > > > Gerard Freriks > +31 620347088 > [email protected] > > Kattensingel 20 > 2801 CA Gouda > the Netherlands > > On 26 Jul 2018, at 10:46, Diego Boscá <[email protected]> wrote: > > You would be surprised to the amount of legacy data with no clinical > content, just because original systems allowed it > > El jue., 26 jul. 2018 10:41, Bert Verhees <[email protected]> escribió: > >> On 26-07-18 09:57, Thomas Beale wrote: >> > Does it make sense to have an empty COMPOSITION.content? >> >> Imagine a visit to a GP, and nothing clinical comes out of it. Nothing >> worth mentioning, but still having had a composition and a consult to >> pay for. >> >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected] >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
