Consider if CapabilityStatement.rest.resource.supportedProfile is correct level to list profiles a system supports - 2018-Jan Core #46

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • CapabilityStatement (Conformance)
    • Hide

      The supportedProfile on rest.resource has a particular meaning around search capabilities. The profiles used to define documents and messages are part of graphdefintition and the other things that define them. If there's a need for the notion of "supportedProfiles" here it would have a different meaning and could be proposed but would likely be distinct from what profiles are supported for rest

      Show
      The supportedProfile on rest.resource has a particular meaning around search capabilities. The profiles used to define documents and messages are part of graphdefintition and the other things that define them. If there's a need for the notion of "supportedProfiles" here it would have a different meaning and could be proposed but would likely be distinct from what profiles are supported for rest
    • Grahame Grieve/Richard Ettema: 8-0-0

      Existing Wording: CapabilityStatement.rest.resource.supportedProfile

      Proposed Wording: Move up to Capability Statement Level

      Comment:

      Did you consider nesting the resource block at the CapabilityStatement root. I am concerned we will need a similar structured under Messages and Documents

      Summary:

      Consider if CapabilityStatement.rest.resource.supportedProfile is correct level to list profiles a system supports

            Assignee:
            Unassigned
            Reporter:
            Brett Marquard
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: