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
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
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 escribió:
> On 26-07-18 09:57, Thomas Beale wrote:
> > Does it make sense to have an empty COMPOSITION.content?
>
> Imagine a visit to
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.
On 04/07/2018 22:49, Pablo Pazos wrote:
Hi all,
Recently a client committed COMPOSITIONS with empty content to the
EHRServer, because in the OPT all the structure was associated to
context.other_context.
After reviewing the specs, I found this invariant on the COMPOSITION spec:
Hi all,
Recently a client committed COMPOSITIONS with empty content to the
EHRServer, because in the OPT all the structure was associated to
context.other_context.
After reviewing the specs, I found this invariant on the COMPOSITION spec:
Content_valid: content /= Void implies not
6 matches
Mail list logo
