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

Define the meaning of Must Support

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot [deprecated]
    • Clinical Decision Support
    • STU
    • (many)
    • Hide

      Agreed, provide a definition of Must Support for the profiles in this IG:

      Certain elements in the profiles defined in this implementation guide are marked as Must Support. This flag is used to indicate that the element plays a critical role in defining and sharing artifacts, and implementations SHALL understand and process the element.

      In addition, because artifact specifications typically make use of data implementation guides (e.g. IPS, US Core, QI-Core), the implications of the Must Support flag for profiles used from those implementation guides must be considered.

      For more information, see the definition of Must Support in the base FHIR specification.

      Conformance Requirement 3.18 (Must Support Elements):

      For resource instances claiming to conform to CRMI IG profiles, Must Support on any profile data element SHALL be interpreted as follows:

      • Authoring systems and knowledge repositories SHALL be capable of populating all Must Support data elements.
      • Evaluating systems SHALL be capable of processing resource instances containing Must Support data elements without generating an error or causing the evaluation to fail.
      • In situations where information on a particular data element is not present and the reason for absence is unknown, authoring and repository systems SHALL NOT include the data elements in the resource instance. For example, for systems using ‘9999’ to indicate unknown data values, do not include ‘9999’ in the resource instance.
      • When consuming resource instances, evaluating systems SHALL interpret missing data elements within resource instances as data not present for the artifact.
      • Submitting and receiving systems using knowledge artifacts to perform data exchange or artifact evaluation operations SHALL respect the must support requirements of the profiles used by the artifact to describe the data involved in the operation.
      Show
      Agreed, provide a definition of Must Support for the profiles in this IG: Certain elements in the profiles defined in this implementation guide are marked as Must Support. This flag is used to indicate that the element plays a critical role in defining and sharing artifacts, and implementations SHALL understand and process the element. In addition, because artifact specifications typically make use of data implementation guides (e.g. IPS, US Core, QI-Core), the implications of the Must Support flag for profiles used from those implementation guides must be considered. For more information, see the definition of Must Support in the base FHIR specification. Conformance Requirement 3.18 (Must Support Elements): For resource instances claiming to conform to CRMI IG profiles, Must Support on any profile data element SHALL be interpreted as follows: Authoring systems and knowledge repositories SHALL be capable of populating all Must Support data elements. Evaluating systems SHALL be capable of processing resource instances containing Must Support data elements without generating an error or causing the evaluation to fail. In situations where information on a particular data element is not present and the reason for absence is unknown, authoring and repository systems SHALL NOT include the data elements in the resource instance. For example, for systems using ‘9999’ to indicate unknown data values, do not include ‘9999’ in the resource instance. When consuming resource instances, evaluating systems SHALL interpret missing data elements within resource instances as data not present for the artifact. Submitting and receiving systems using knowledge artifacts to perform data exchange or artifact evaluation operations SHALL respect the must support requirements of the profiles used by the artifact to describe the data involved in the operation.
    • Floyd Eisenberg / Rob McClure: 18-0-0
    • Enhancement
    • Compatible, substantive

    Description

      Must Support flags are used in many artifacts of this guide, yet the definition of must support is not provided. The definition of Must Support could have significant repercussions for the requirements laid out in this IG and needs to be defined. This is of particular importance as this is an IG for implementers of technology (e.g. those creating a knowledge repository) and for implementers of IGs that fall under the scope of this IG and are possibly expected to conform to it. Many of the profiles have items listed as MS, and as it stands are impossible to comment/vote on without a definition. With a definition in place, we may need to re-evaluate the MS flags on those elements.

      Attachments

        Activity

          People

            Unassigned Unassigned
            corey_spears Corey Spears
            Corey Spears
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: