FHIR Chat · US core profile · implementers

Stream: implementers

Topic: US core profile


view this post on Zulip Pranitha Sruthi (Dec 07 2017 at 04:58):

Hi @Michel Rutten when I tried to import US core MedicationRequest profile on forge, an error is getting displayed medicationreq.PNG Moreover, I did not uncheck the 'Is modifier' option and is not getting checked when I click on it. Please help me fix the error. Thank you

view this post on Zulip Michel Rutten (Dec 07 2017 at 10:31):

Hi @Pranitha Sruthi, looks like you've discovered both an error in the US Core profile as a bug in the application.
FHIR MedicationRequest resource defines the element MedicationRequest.status with IsModifier = true.
The US Core MedicationRequest profile defines MedicationRequest.status with IsModifier = false (in differential).
This is illegal; if a base profile marks an element as modifier, then derived profiles are not allowed to override this.
So the warning in Forge is correct. However it appears that Forge does not let you correct the invalid value. This is a bug in the application.
I suggest you report this issue to the author of the US Core MedicationRequest profile.
I'll try to fix the bug in Forge. Thank you for reporting!

view this post on Zulip Pranitha Sruthi (Dec 07 2017 at 10:33):

Ok may I know who is the author and how can I report? I have faced the same problem with the US core MedicationStatement profile as well.

view this post on Zulip Michel Rutten (Dec 07 2017 at 11:01):

Hi @Pranitha Sruthi, the profile itself states Publisher = "HL7 US Realm Steering Committee", Contact URL = http://www.healthit.gov. So the ONC is responsible for this profile.
I've already managed to fix the UI issue in Forge. The next release will allow you to correct invalid IsModifier attributes.

view this post on Zulip Grahame Grieve (Dec 07 2017 at 11:02):

actually, @Eric Haas and @Brett Marquard are the editors

view this post on Zulip Eric Haas (Dec 07 2017 at 17:29):

actually US Core is an HL7 artifact and you report trackers using GForge just like reporting trackers for the base specification.. That is true for any HL7 FHIR artifact. If you read the US Core home page you will see these direction and a link to GForge. @Michel Rutten I didn't define the ismodifier field in differential for anything in US Core (unless its a typo or copy paste error.) so I would assume it would not change from the base. Will investigate though.

view this post on Zulip Eric Haas (Dec 07 2017 at 21:45):

This seems like an ig-pub issue. @Grahame Grieve all the elements have ismod = false:

   <element id="Communication.status">
      <path value="Communication.status"/>
      <short value="eICR Processing Status"/>
      <definition
                  value="The status of eICR processing, including an acknowledgemen of successful processing or any known errors encountered during eICR processing."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="code"/>
      </type>
      <mustSupport value="true"/>
      <isModifier value="false"/>
      <binding>
  ~~~

view this post on Zulip Eric Haas (Dec 07 2017 at 22:25):

it is an issue with the ig-pub - no matter if generated from a spreadsheet or SD file. The isMods are not inherited from the base.

view this post on Zulip Eric Haas (Dec 08 2017 at 00:24):

GF#14278

view this post on Zulip Eric Haas (Dec 09 2017 at 15:42):

@Brett Marquard FYI


Last updated: Apr 12 2022 at 19:14 UTC