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

Correct unclear Profile conformance guidance

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • 3.0.0-ballot [deprecated]
    • Clinical Interoperability Council
    • STU
    • Profile Conformance
    • Profile-Level Conformance Expectations
    • Hide

      The reviewer questions whether our guidance on validation when `meta.profile` is absent is appropriate. In response, we have reviewed the language of section 10.2 (Profile-Level Conformance Expectations) and believe that it is both correct and clear. In particular, we give contingencies for the data receiver, if `meta.profile` is missing:

      1) The data receiver may examine the instance contents to try and associate it with a profile. Often, there is an identifying code or category that can be used to associate an instance with a profile.

      2) As a last resort, the data receiver may have to iterate through its supported profiles for that resource, to find a profile that the resource validates against.

      We believe the description is both accurate and clear, and does not need to be revised.

      Show
      The reviewer questions whether our guidance on validation when `meta.profile` is absent is appropriate. In response, we have reviewed the language of section 10.2 (Profile-Level Conformance Expectations) and believe that it is both correct and clear. In particular, we give contingencies for the data receiver, if `meta.profile` is missing: 1) The data receiver may examine the instance contents to try and associate it with a profile. Often, there is an identifying code or category that can be used to associate an instance with a profile. 2) As a last resort, the data receiver may have to iterate through its supported profiles for that resource, to find a profile that the resource validates against. We believe the description is both accurate and clear, and does not need to be revised.
    • Saul Kravitz / Jimmy Tcheng : 7 - 0 - 0

    Description

      The expectation for this guidance seems questionable from the perspective of determining profile conformance from elements outside of .meta (which is considered bad practice) 

      If meta.profile is not populated, then the data receiver will need to validate the instance against expected profile(s) to see if it conforms to any.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Jeff_Brown Jeff Brown
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: