Capstatement is Incomplete

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US CARIN Real-time Pharmacy Benefit Check (RTPBC) (FHIR)
    • 0.1.0
    • Pharmacy
    • Capability Statements
    • Hide

      Modify the responder capability statement page and resource to include:

      • SHALL suport the process-message operation (http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message)
      • SHALL Support at least one use case defined in this Guide and listed in the Use Cases page, Section. 1.
      • SHALL implement the RESTful behavior according to the FHIR specification.
        • 1. Support the JSON source format.
        • 2. Provide on the server a CapabilityStatement identifying the profiles supported.
      • SHOULD: 1. Support the xml source format. 2. Identify the CARIN RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance created.

      Add a requester capability statement that includes:

      • SHALL Support at least one use case defined in this Guide and listed in the Use Cases page, section 1)
      • SHALL implement the RESTful behavior according to the FHIR specification.
        • 1. Support the JSON source format.
      • SHOULD: 1. Identify the CARIN RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance.
      • May support the xml source format

       Ensure the narrative in the respective IG pages matches the associated CapabilityResource contents.

      Show
      Modify the responder capability statement page and resource to include: SHALL suport the process-message operation ( http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message) SHALL Support at least one use case defined in this Guide and listed in the Use Cases page, Section. 1. SHALL implement the RESTful behavior according to the FHIR specification. 1. Support the JSON source format. 2. Provide on the server a CapabilityStatement identifying the profiles supported. SHOULD: 1. Support the xml source format. 2. Identify the CARIN RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance created. Add a requester capability statement that includes: SHALL Support at least one use case defined in this Guide and listed in the Use Cases page, section 1) SHALL implement the RESTful behavior according to the FHIR specification. 1. Support the JSON source format. SHOULD: 1. Identify the CARIN RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance. May support the xml source format  Ensure the narrative in the respective IG pages matches the associated CapabilityResource contents.
    • Pooja Babbrah / Jean Duteau : 8-0-1
    • Enhancement
    • Compatible, substantive
    • 0.1.0

      • Capstatement is Incomplete

      The Capstatement consists of .... "Declare a CapabilityStatement identifying the profiles supported"

      This is just pushing the heavy lifting off to the implementers. IG Should show exactly how to do this.

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

              Created:
              Updated:
              Resolved: