Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-33029

Mark mandatory top level elements MUST SUPPORT

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US QI Core (FHIR)
    • 2.0 [deprecated]
    • Clinical Quality Information
    • QICore Claim
    • QI-Core Profiles
    • Hide

      QI Core section 1.12 addresses Must Support requirements and references US Core requirements via a link. That link currently goes to the full US Core page General Guidance. Will change that link to the specific section of the US page 2.2 Must Support. This guidance specifically states, "The Profile elements consist of both Mandatory and Must Support elements. Mandatory elements are elements with an minimum cardinality of 1 (min=1). The base FHIR Must Support guidance requires specifications to define exactly the support expected for profile elements labeled Must Support. The sections below illustrate how these elements are displayed and define the rules for interpreting profile elements and subelements labeled Mandatory and Must Support for requesters and responders."
      To provide further support, will assure that all elements with cardinality of 1.. have a Must Support flag, and further that only subelements with cardinality of 1.. that are part of Must Support elements will also be tagged as Must Support.

      Show
      QI Core section 1.12 addresses Must Support requirements and references US Core requirements via a link. That link currently goes to the full US Core page General Guidance . Will change that link to the specific section of the US page 2.2 Must Support . This guidance specifically states, "The Profile elements consist of both Mandatory and Must Support elements. Mandatory elements are elements with an minimum cardinality of 1 (min=1). The base FHIR Must Support guidance requires specifications to define exactly the support expected for profile elements labeled Must Support. The sections below illustrate how these elements are displayed and define the rules for interpreting profile elements and subelements labeled Mandatory and Must Support for requesters and responders." To provide further support, will assure that all elements with cardinality of 1.. have a Must Support flag, and further that only subelements with cardinality of 1.. that are part of Must Support elements will also be tagged as Must Support.
    • Abdulah Rafiqi/Ben Hamlin 13-0-0
    • Enhancement
    • Non-compatible

    Description

      When a top level element in a resource has cardinality 1.. (i.e., mandatory), it should be marked as MUST SUPPORT (MS).  Review all QI-Core profiles and make sure MS is set for mandatory top level elements.

      This is consistent with http://hl7.org/fhir/us/core/conformance-expectations.html#mandatory-elements

      QI-Core profiles that do not derive from US Core should be examined.

      For example, Claim has .status, .type, .use, and .priority currently not marked as MS.

      QI-Core profiles that derive from US Core are probably ok.

      Do we need to also mark 2nd level 1.. elements as MS if it's parent element is MS (but not necessarily mandatory)?

       

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            mitrep9g Paul Denning
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: