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

Why is Procedure.category binding example when other category bindings are extensible?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive with Modification
    • Specification:
      US SDOH Clinical Care (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Patient Care
    • Related Artifact(s):
      SDOHCC Procedure Base 1
    • Grouping:
    • Resolution Description:
      Hide

      Add standard extension (pre adopt R5) to support multiple categories and add invariant to require our value set in either the category element or the extension

      Show
      Add standard extension (pre adopt R5) to support multiple categories and add invariant to require our value set in either the category element or the extension
    • Resolution Vote:
      Bob Dieterle / Jay Lyle : 7-0-3
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      Observation and serviceRequest both have required bindings. You could make it extensible if the concern is that you want to allow other things.

      (Comment 156 - imported by: Robert Dieterle)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              lloyd Lloyd McKenzie
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: