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

must support should require population if known

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • International Patient Summary (FHIR)
    • current
    • Patient Care
    • Design Conventions and Principles
    • 3.4
    • Hide

      The proposed resolution is to use the revised Must Support language developed as part of the must-support-review branch. A significant R2/RK review of ISO 27269 was included in this branch. 

      Implementers conforming to a particular profile in the IPS Implementation Guide:

      • SHALL be capable of producing values for the mustSupport elements in the profile (see 3.4.1 for handling of missing data)
      • SHALL be capable of processing resource instances containing mustSupport data elements, including elements with missing data, without generating an error or causing the application to fail.
      • SHOULD be capable of displaying mustSupport data elements for human use, or processing (e.g. storing) them for other purposes.

      Implementers conforming to an IPS document in the IPS Implementation Guide:

      • SHALL be capable of supporting profiles under sections that are marked mustSupport in the IPS Composition profile
      • SHALL be capable of populating profiles for allergy, medication and problem information in an IPS document

       

      Show
      The proposed resolution is to use the revised Must Support language developed as part of the must-support-review branch. A significant R2/RK review of ISO 27269 was included in this branch.  Implementers conforming to a particular profile in the IPS Implementation Guide: SHALL be capable of producing values for the mustSupport elements in the profile (see  3.4.1  for handling of missing data) SHALL be capable of processing resource instances containing mustSupport data elements, including elements with missing data, without generating an error or causing the application to fail. SHOULD be capable of displaying mustSupport data elements for human use, or processing (e.g. storing) them for other purposes. Implementers conforming to an IPS document in the IPS Implementation Guide: SHALL be capable of supporting profiles under sections that are marked mustSupport in the IPS Composition profile SHALL be capable of populating profiles for allergy, medication and problem information in an IPS document  
    • John DAmore / Gay Dolin : 13-0-17
    • Enhancement
    • Compatible, substantive
    • current

    Description

      It is common, in IHE, for MustSupport to also require a publisher to include the elements marked MustSupport if they have the data to populate that element. This is similar to past use of R2 or RE. This seems still reasonable today. The definition in IPS does not require that I populate MS elements when I have the data. It simply requires that I be "able" to populate them. This "able to populate" seems very ambiguous, where as must populate when the data are known is far more executable and testable.

      Attachments

        Activity

          People

            Unassigned Unassigned
            john_moehrke John Moehrke
            John Moehrke
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: