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

Disagree with the addition of CodeableReference data type

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • STU
    • References
    • Hide

      This data type was introduced in R4B and it is too late to remove it now. The balloter may choose to comment on specific resources in R5 where it's been introduced and they feel the addition is not justified. However, there is no expectation for backwards compatibility between R5 and R4 for any resources that were not normative in R4. Reference of R4 in regulation in any particular country doesn't introduce such an expectation. The introduction of this data type significantly simplifies referencing where there are collections of references that might be CodeableConcepts or proper References. Ordering such collections is not possible without this data type.

      Show
      This data type was introduced in R4B and it is too late to remove it now. The balloter may choose to comment on specific resources in R5 where it's been introduced and they feel the addition is not justified. However, there is no expectation for backwards compatibility between R5 and R4 for any resources that were not normative in R4. Reference of R4 in regulation in any particular country doesn't introduce such an expectation. The introduction of this data type significantly simplifies referencing where there are collections of references that might be CodeableConcepts or proper References. Ordering such collections is not possible without this data type.
    • Rick Geimer/Grahame Grieve: 8-0-2

    Description

      We disagree with the addition of the CodeableReference data type. This change is not backwards compatible, and at least in the US, we expect widespread implementation of R4 through 21st Century Cures.  If the goal is to allow both a CodeableConcept and a Reference to be provided, this constraint (at least one required) could be noted in the textual descriptions of the two fields and enforced by the Schematron.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hstrasbe Howard Strasberg
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: