CapabilityStatement - operations shouldn't be normative

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Normative
    • CapabilityStatement (Conformance)
    • operations
    • 5.2.1
    • Hide

      Mark these operations as [TU]

      Show
      Mark these operations as [TU]
    • Grahame Grieve/Lloyd McKenzie: 3-0-0
    • Correction
    • Non-substantive
    • STU3

      The capabilityStatement resource is marked for normative - the operations should not be included in this as I do not believe they have seen wide use ($subset, $implements, $conforms).

            Assignee:
            Unassigned
            Reporter:
            Danielle Friend
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: