FHIR Chat · unmarshalling error · IG creation

Stream: IG creation

Topic: unmarshalling error


view this post on Zulip Brian Reinhold (Sep 20 2018 at 09:29):

I am getting errors like this from all my CodeSystem and ValueSet resources

Error unmarshalling resource: Unable to provide support for code system urn:iso:std:iso:11073:10101

I have no idea what this means or what I need to do to fix it. I can't find any description of these error messages on the Wiki so I am not sure how to solve this. Anyone understand what these errors are caused by? (The pages still build.)

view this post on Zulip Stefan Karl (Sep 20 2018 at 11:17):

I'm getting the same error when building the PoCD IG. Most probably the terminology server does not know about the MDC code system (urn:iso:std:iso:11073:10101).

view this post on Zulip Brian Reinhold (Sep 20 2018 at 15:10):

I'm getting the same error when building the PoCD IG. Most probably the terminology server does not know about the MDC code system (urn:iso:std:iso:11073:10101).

If that is the case then I can understand the related errors pointing to my CodeSystems.

view this post on Zulip Grahame Grieve (Sep 21 2018 at 02:09):

the terminology server does indeed not know about the code system. All we have to do is produce a code system resource, and then we can upload it to the server

view this post on Zulip Stefan Karl (Sep 21 2018 at 08:43):

@Grahame Grieve This is what I created a while ago:

<?xml version="1.0" encoding="UTF-8"?>
<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="MDC"/>
  <url value="urn:iso:std:iso:11073:10101"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.6.24"/>
  </identifier>
  <name value="MDC"/>
  <title value="MDC Nomenclature"/>
  <status value="draft"/>
  <experimental value="false"/>
  <publisher value="Health Level Seven International (Health Care Devices Work Group)"/>
  <description value="ISO/IEEE 11073-10101 Nomenclature for point-of-care medical device communication."/>
  <content value="not-present"/>
  <property>
    <code value="status"/>
    <description value="Status of the term code in NIST RTMMS."/>
    <type value="Coding"/>
  </property>
  <property>
    <code value="harmonized"/>
    <description value="Indicates whether the term code has been agreed upon during the open consensus-based Rosetta harmonization process."/>
    <type value="boolean"/>
  </property>
  <property>
    <code value="partition"/>
    <description value="Partition is a group of semantics that are assigned to a contiguous term code range and have a categorical relationship."/>
    <type value="code"/>
  </property>
</CodeSystem>

Would this be sufficient to make it a "known" code system? Obviously there are no concepts included. These should come from the RTMMS database, where some information is still missing in the exported data. But it's on my ToDo list.

view this post on Zulip Brian Reinhold (Sep 21 2018 at 08:44):

the terminology server does indeed not know about the code system. All we have to do is produce a code system resource, and then we can upload it to the server

@Grahame Grieve I have a few CodeSystem resources I have made that are stand-a-lone. Could these be uploaded to the server?

view this post on Zulip Grahame Grieve (Sep 21 2018 at 10:53):

if tx.fhir.org is going to use it, it needs all the concepts. Is this the properties that the committee agrreed to?

view this post on Zulip Stefan Karl (Sep 21 2018 at 10:59):

Yes, it has been discussed and written down in the DoF WG. There is one more time slot reserved for this topic during the Baltimore meeting.


Last updated: Apr 12 2022 at 19:14 UTC