Define what it means when CapStatement elements lack an expectation -extension

XMLWordPrintableJSON

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

      Add a note to the section 5.2.1.3 (where the different types of CapabilityStatement are described) that says that:

      CapabilityStatements of type "requirement" describe what capabilities are potentially relevant, additional documentation or extensions (<add reference to existing extension>) within the CapStat are expected to make more explicit statements of degree of expectation associated with each capability.

      Add an example of a requirement capabilitystatement that uses the extension.

      Show
      Add a note to the section 5.2.1.3 (where the different types of CapabilityStatement are described) that says that: CapabilityStatements of type "requirement" describe what capabilities are potentially relevant, additional documentation or extensions (<add reference to existing extension>) within the CapStat are expected to make more explicit statements of degree of expectation associated with each capability. Add an example of a requirement capabilitystatement that uses the extension.
    • Lloyd McKenzie/Eric Haas: 7-0-0
    • Clarification
    • Non-substantive
    • STU3

      When using CapStatement to define expectations what does it mean when the expectation extension is empty

      see Zulip chat:

      https://chat.fhir.org/#narrow/stream/23-conformance/topic/expectation.20when.20no.20extension.2E

      I propose it means it is undefined.

            Assignee:
            Unassigned
            Reporter:
            Eric Haas
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: