A question about the XML schema for version 1.4 archetypes

Technical (archive)
1

I have a question about the XML schema for archetypes based on ADL version 1.4

The set of schemas we are using to validate XML archetype exports are 1.0.1

ETC..

The issue we are getting is that sometimes an archetype has a tag. All those downloaded from our CKM (ckm.hscic.gov.uk) have this tag, but it’s not present on all archetypes from other CKMs (which may be why this could be a new issue).

The schema is expecting the tag before the <archetype_id> tag

<xs:complexType name=“ARCHETYPE”>

xs:complexContent

<xs:extension base=“AUTHORED_RESOURCE”>

xs:sequence

<xs:element name=“uid” type**=“HIER_OBJECT_ID”** minOccurs**=“0”/>**

<xs:element name=“archetype_id” type=“ARCHETYPE_ID”/>

<xs:element name=“adl_version” type=“xs:string” minOccurs=“0”/>

However, in the XML instances, the (if present) appears after the <adl_version> tag

<archetype_id>

openEHR-EHR-OBSERVATION.newborn_birth_details.v0

</archetype_id>

<adl_version>1.4</adl_version>

<uid>7f716e0e-5fa8-4fec-942d-208764409b07</uid>

Further, changing the schema to change the expected tag order to match the XML instances shows up a further issue in that the format of (according to the schema) should use a tag like this

7f716e0e-5fa8-4fec-942d-208764409b07

Are we using an out of date set of schema? Or are these known issues? Have people corrected the schema for their own use (if so could I have a copy please)?

Kind regards

Dave Barnet
Interoperability Lead

Interoperability Specifications

Health & Social Care Information Centre
david.barnet@hscic.gov.uk
www.hscic.gov.uk

2

I have a question about the XML schema for archetypes based on ADL version 1.4

The set of schemas we are using to validate XML archetype exports are 1.0.1

ETC..

The issue we are getting is that sometimes an archetype has a

The schema is expecting the tag before the <archetype_id> tag

<xs:complexType name=“ARCHETYPE”>

xs:complexContent

<xs:extension base=“AUTHORED_RESOURCE”>

xs:sequence

<xs:element name=“uid” type**=“HIER_OBJECT_ID”** minOccurs**=“0”/>**

<xs:element name=“archetype_id” type=“ARCHETYPE_ID”/>

<xs:element name=“adl_version” type=“xs:string” minOccurs=“0”/>

However, in the XML instances, the (if present) appears after the <adl_version> tag

<archetype_id>

openEHR-EHR-OBSERVATION.newborn_birth_details.v0

</archetype_id>

<adl_version>1..4</adl_version>

<uid>7f716e0e-5fa8-4fec-942d-208764409b07</uid>

Further, changing the schema to change the expected tag order to match the XML instances shows up a further issue in that the format of (according to the schema) should use a tag like this

7f716e0e-5fa8-4fec-942d-208764409b07

Are we using an out of date set of schema? Or are these known issues? Have people corrected the schema for their own use (if so could I have a copy please)?

Kind regards

Dave Barnet
Interoperability Lead

Interoperability Specifications

Health & Social Care Information Centre
david.barnet@hscic.gov.uk
www.hscic.gov.uk

3

Hi Dave and all,

This is the Java XML Serialiser generating XML from ADL on the fly in the CKM.

The archetype editor is doing it “your” way as well, and I would assume this is correct.

I am a bit surprised this is happening, because I am pretty sure we looked in depth at any the differences a while ago, comparing XML in the Archetype Editor to XML generated in CKM by the Java XML Serialiser.

All new archetypes now receive a uid as part of their identification (including on other ckms), but before that pretty much nobody was using this field, so it may be that we just did not notice.

So, my understanding is that this is a bug in the Java XML serialisation.
If nobody contradicts me, I’ll have a look and fix it in there.

Sebastian

4

Can someone help to take me off the list. I have signed into the list and unsubscribe and still unsuccessful.

5

Hi Dave,

This has been fixed now - please have a look in case there are any problems.

Regards
Sebastian

6

Hi Sebastian

I’ve tested a dozen or so archetypes from various CKMs, (some with and some without), and all the XML downloads verify against the schema.

Thanks very much for the fix

Dave Barnet

(attachments)

WRD0000.jpg