Hi Dave,
This has been fixed now - please have a look in case there are any problems.
Regards
Sebastian
On 03.09.2015 17:23, Sebastian Garde wrote:
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
On 03.09.2015 15:38, [email protected] wrote:
Hi, the uid might be assigned by the archetype editor, before
uploading the adl into the ckm, so this can be a bug on the AE.
Sent from my LG Mobile
------ Original message------
*From: *Barnet David (HEALTH AND SOCIAL CARE ...
*Date: *Thu, Sep 3, 2015 10:31
*To: *[email protected];
*Subject:*A question about the XML schema for version 1.4 archetypes
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
<!--openEHR Release 1.0.1 OpenehrProfile XML schema-->
<!--openEHR Release 1.0.1 Archetype XML schema-->
<!--openEHR Release 1.0.1 BaseTypes XML schema-->
ETC..
The issue we are getting is that sometimes an archetype has a tag.
All those downloaded from our CKM (ckm.hscic.gov.uk
<http://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 <uid> tag before the <archetype_id> tag
<xs:complexTypename="ARCHETYPE">
<xs:complexContent>
<xs:extensionbase="AUTHORED_RESOURCE">
<xs:sequence>
*<**xs:element**name**="**uid**"**type**="**HIER_OBJECT_ID**"**minOccurs**="**0**"/>***
<xs:elementname="archetype_id"type="ARCHETYPE_ID"/>
<xs:elementname="adl_version"type="xs:string"minOccurs="0"/>
However, in the XML instances, the <uid> (if present) appears after
the <adl_version> tag
<archetype_id>
<value>openEHR-EHR-OBSERVATION.ne
<http://openEHR-EHR-OBSERVATION.ne>wborn_birth_details.v0</value>
</archetype_id>
<adl_version>1..4</adl_version>
*<**uid**>**7f716e0e-5fa8-4fec-942d-208764409
<tel:208764409>b07**</**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 <uid> (according to the schema) should use a <value> tag like this
<uid>
<value>7f716e0e-5fa8-4fec-942d-208764409 <tel:208764409>b07</value>
</uid>
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
<mailto:[email protected]>[email protected]
<http://www.hscic.gov.uk>www.hscic.gov.uk <http://www.hscic.gov.uk>
********************************************************************************************************************
This message may contain confidential information. If you are not the
intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do 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.
Thank you for your co-operation.
NHSmail is the secure email and directory service available for all
NHS staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive
information with NHSmail and GSi recipients
NHSmail provides an email address for your career in the NHS and can
be accessed anywhere
********************************************************************************************************************
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
--
*Dr. Sebastian Garde*
/Dr. sc. hum., Dipl.-Inform. Med, FACHI/
Ocean Informatics
Skype: gardeseb
------------------------------------------------------------------------
Avast logo <https://www.avast.com/antivirus>
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
www.avast.com <https://www.avast.com/antivirus>
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
--
*Dr. Sebastian Garde*
/Dr. sc. hum., Dipl.-Inform. Med, FACHI/
Ocean Informatics
Skype: gardeseb
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
