Re: Empty COMPOSITION.content is valid?

[Ian McNicoll]

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: i...@freshehr.com
twitter: @ianmcnicoll


Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL


On Thu, 26 Jul 2018 at 09:59, GF  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
>   gf...@luna.nl
>
> Kattensingel  20
> 2801 CA Gouda
> the Netherlands
>
> On 26 Jul 2018, at 10:46, Diego Boscá  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  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
>> openEHR-technical@lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Empty COMPOSITION.content is valid?

[GF]

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
  gf...@luna.nl

Kattensingel  20
2801 CA Gouda
the Netherlands

> On 26 Jul 2018, at 10:46, Diego Boscá  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  > 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
> openEHR-technical@lists.openehr.org 
> 
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org 
> 
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org



signature.asc
Description: Message signed with OpenPGP
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Empty COMPOSITION.content is valid?

[Diego Boscá]

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 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
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Empty COMPOSITION.content is valid?

[Bert Verhees]

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
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Empty COMPOSITION.content is valid?

[Thomas Beale]

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:

Content_valid: content /= Void implies not content.is_empty

That means that content can actually be null/void, since on that case, 
the "implies" is true.


this is indeed what the spec says.


Also checked the COMPOSITION XSD, and the minOccurs for content is 0.

Does it make sense to have an empty COMPOSITION.content?
Does other implementers support that?


This is certainly the way to decide whether Void is allowed or not.

- thomas

___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Empty COMPOSITION.content is valid?

[Pablo Pazos]

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 content.is_empty

That means that content can actually be null/void, since on that case, the
"implies" is true.

Also checked the COMPOSITION XSD, and the minOccurs for content is 0.

Does it make sense to have an empty COMPOSITION.content?
Does other implementers support that?
On which cases?

Thanks!

-- 
*Ing. Pablo Pazos Gutiérrez*
pablo.pa...@cabolabs.com
+598 99 043 145
skype: cabolabs
Subscribe to our newsletter 

http://www.cabolabs.com
https://cloudehrserver.com
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org