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

Change binding for Condition.category back to Extensible

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • Patient Care
    • STU
    • Condition
    • Hide

      The profiles in an implementation guide can further restrict the binding strength (to extensible) as needed, so the base spec should remain preferred.

      For example, the IPS IG does have an additional value set defined for LOINC Problem that would not be possible if the base spec restricts to extensible.

      Show
      The profiles in an implementation guide can further restrict the binding strength (to extensible) as needed, so the base spec should remain preferred. For example, the IPS IG does have an additional value set defined for LOINC Problem that would not be possible if the base spec restricts to extensible.
    • Rob Hausam / Jay Lyle : 5-0-0

    Description

      For Condition.category, we disagree with the change in binding from Extensible to Preferred. The category information is important clinically, so we think the binding should remain Extensible.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: