Sam Heard wrote:
> Hi Adam
>
> I take this point and in that case I would suggest that resulting
> issue to discuss is:
>
> Should we drop the class name from the Archetype Slot in ADL and just
> use the regex? There does not appear to be any reason in the AOM to
> include the class name. We do need the occurrences for the slot.
>
> allow_archetype CLUSTER occurrences matches {0..5} matches {
> include
> archetype_id/value matches
> {/exam\.v1|exam-uterus\.v1|exam-fetus\.v1/}
>
> might become:
>
> allow_archetype occurrences matches {0..5} matches {
> include
> archetype_id/value matches
> {/openEHR-EHR-CLUSTER\.exam\.v1|openEHR-EHR-CLUSTER\.exam-uterus\.v1|openEHR-EHR-CLUSTER\.exam-fetus\.v1/}
>
> This would have advantages in controlling ordering of included
> archetypes of mixed classes.
>
> Interested in others views.
>
> Cheers, Sam
That would be fine by me.
That would allow me to drop my "regex pre-processor" which would be nice
& would give me some peace of mind wrt people using regex.
Adam
***********************************************************************
This message may contain confidential and privileged information.
If you are not the intended recipient you should not disclose, copy
or distribute information in this e-mail or take any action in reliance
on its contents. To do so is strictly prohibited and may be unlawful.
Please inform the sender that this message has gone astray before
deleting it. Thank you.
2008 marks the 60th anniversary of the NHS. It's an opportunity to pay
tribute to the NHS staff and volunteers who help shape the service, and
celebrate their achievements.
If you work for the NHS and would like an NHSmail email account, go
to: www.connectingforhealth.nhs.uk/nhsmail
***********************************************************************