FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource CapabilityStatement/FHIR Server from package hl7.fhir.fi.smart#current (78 ms)

Package hl7.fhir.fi.smart
Type CapabilityStatement
Id Id
FHIR Version R4
Source https://hl7.fi/fhir/finnish-smart/https://build.fhir.org/ig/fhir-fi/finnish-smart/CapabilityStatement-fi-smart-server.html
Url https://hl7.fi/fhir/finnish-smart/CapabilityStatement/fi-smart-server
Version 1.0.1-cibuild
Status active
Date 2023-11-09
Name FiSmartServer
Title Finnish SMART Server Capability Statement
Experimental False
Realm fi
Authority hl7
Description This CapabilityStatement describes the basic rules for a server actor providing SMART App Launch in Finland.
Kind requirements

Resources that use this resource

No resources found


Resources that this resource uses

ImplementationGuide
http://hl7.org/fhir/uv/ipa/ImplementationGuide/hl7.fhir.uv.ipa International Patient Access
http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch SMART App Launch


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: CapabilityStatement fi-smart-server

Finnish SMART Server Capability Statement

  • Implementation Guide Version: 1.0.1-cibuild
  • FHIR Version: 4.0.1
  • Supported Formats: SHALL support json, SHOULD support xml
  • Supported Patch Formats: SHOULDsupport application/json-patch+json
  • Published on: 2023-11-09
  • Published by: HL7 Finland ry

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

SHALL Support the Following Implementation Guides

SHOULD Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

The server SHALL:

  1. Implement the RESTful behavior according to the FHIR specification.
  2. Support JSON source formats for all interactions.
  3. Declare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.

The server SHOULD:

  1. Support XML source formats for all interactions.
  2. Implement the International Patient Access (IPA) specification.
Security

This implementation guide relies heavily on the widely adopted SMART App Launch mechanism. This implementation guide does not define any new security mechanisms. Please familiarize yourself with the securty concepts infroduced in the SMART App Launch specification, and the underlying OpenID Connect and OAuth2 specifications the SMART App Launch specification build on.

  1. See the Best Practices outlined in the SMART App Launch specification.
  2. See the FHIR Security section of the FHIR specification for requirements and recommendations.
  3. A server SHALL reject any unauthorized requests by returning an HTTP 401 Unauthorized, 403 Forbidden, or 404 Not Found response code.
Summary of System-wide Interactions

Source

{
  "resourceType" : "CapabilityStatement",
  "id" : "fi-smart-server",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CapabilityStatement fi-smart-server</b></p><a name=\"fi-smart-server\"> </a><a name=\"hcfi-smart-server\"> </a><a name=\"fi-smart-server-fi-FI\"> </a><h2 id=\"title\">Finnish SMART Server Capability Statement</h2><ul><li>Implementation Guide Version: 1.0.1-cibuild </li><li>FHIR Version: 4.0.1 </li><li>Supported Formats: <strong>SHALL</strong> support <code>json</code>, <strong>SHOULD</strong> support <code>xml</code></li><li>Supported Patch Formats: <strong>SHOULD</strong>support <code>application/json-patch+json</code></li><li>Published on: 2023-11-09 </li><li>Published by: HL7 Finland ry </li></ul><blockquote class=\"impl-note\"><p><strong>Note to Implementers: FHIR Capabilities</strong></p><p>Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.</p></blockquote><h3 id=\"shallIGs\">SHALL Support the Following Implementation Guides</h3><ul><li><a href=\"http://hl7.org/fhir/smart-app-launch/STU2.1/ImplementationGuide-hl7.fhir.uv.smart-app-launch.html\">http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch</a></li></ul><h3 id=\"shouldIGs\">SHOULD Support the Following Implementation Guides</h3><ul><li><a href=\"http://hl7.org/fhir/uv/ipa/STU1/ImplementationGuide-hl7.fhir.uv.ipa.html\">http://hl7.org/fhir/uv/ipa/ImplementationGuide/hl7.fhir.uv.ipa</a></li></ul><h2 id=\"rest\">FHIR RESTful Capabilities</h2><div class=\"panel panel-default\"><div class=\"panel-heading\"><h3 id=\"mode1\" class=\"panel-title\">Mode: <code>server</code></h3></div><div class=\"panel-body\"><div><p>The server <strong>SHALL</strong>:</p>\n<ol>\n<li>Implement the RESTful behavior according to the FHIR specification.</li>\n<li>Support JSON source formats for all interactions.</li>\n<li>Declare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.</li>\n</ol>\n<p>The server <strong>SHOULD</strong>:</p>\n<ol>\n<li>Support XML source formats for all interactions.</li>\n<li>Implement the International Patient Access (IPA) specification.</li>\n</ol>\n</div><div class=\"lead\"><em>Security</em></div><blockquote><div><p>This implementation guide relies heavily on the widely adopted SMART App Launch mechanism. This implementation guide does not define any new security mechanisms. Please familiarize yourself with the securty concepts infroduced in the SMART App Launch specification, and the underlying OpenID Connect and OAuth2 specifications the SMART App Launch specification build on.</p>\n<ol>\n<li>See the Best Practices outlined in the SMART App Launch specification.</li>\n<li>See the <a href=\"https://www.hl7.org/fhir/security.html\">FHIR Security</a> section of the FHIR specification for requirements and recommendations.</li>\n<li>A server <strong>SHALL</strong> reject any unauthorized requests by returning an HTTP <code>401 Unauthorized</code>, <code>403 Forbidden</code>, or <code>404 Not Found</code> response code.</li>\n</ol>\n</div></blockquote><div class=\"lead\"><em>Summary of System-wide Interactions</em></div></div></div></div>"
  },
  "url" : "https://hl7.fi/fhir/finnish-smart/CapabilityStatement/fi-smart-server",
  "version" : "1.0.1-cibuild",
  "name" : "FiSmartServer",
  "title" : "Finnish SMART Server Capability Statement",
  "status" : "active",
  "date" : "2023-11-09",
  "publisher" : "HL7 Finland ry",
  "contact" : [
    {
      "name" : "HL7 Finland ry",
      "telecom" : [
        {
          "system" : "url",
          "value" : "https://www.hl7.fi/"
        },
        {
          "system" : "email",
          "value" : "mikael@sensotrend.com"
        }
      ]
    }
  ],
  "description" : "This CapabilityStatement describes the basic rules for a server actor providing SMART App Launch in Finland.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "urn:iso:std:iso:3166",
          "code" : "FI",
          "display" : "Finland"
        }
      ]
    }
  ],
  "kind" : "requirements",
  "fhirVersion" : "4.0.1",
  "format" : [
    "json",
    "xml"
  ],
  "_format" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHALL"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    }
  ],
  "patchFormat" : [
    "application/json-patch+json"
  ],
  "_patchFormat" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    }
  ],
  "implementationGuide" : [
    "http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch",
    "http://hl7.org/fhir/uv/ipa/ImplementationGuide/hl7.fhir.uv.ipa"
  ],
  "_implementationGuide" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHALL"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    }
  ],
  "rest" : [
    {
      "mode" : "server",
      "documentation" : "The server **SHALL**:\n1. Implement the RESTful behavior according to the FHIR specification.\n1. Support JSON source formats for all interactions.\n1. Declare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.\n\nThe server **SHOULD**:\n1. Support XML source formats for all interactions.\n1. Implement the International Patient Access (IPA) specification.",
      "security" : {
        "description" : "This implementation guide relies heavily on the widely adopted SMART App Launch mechanism. This implementation guide does not define any new security mechanisms. Please familiarize yourself with the securty concepts infroduced in the SMART App Launch specification, and the underlying OpenID Connect and OAuth2 specifications the SMART App Launch specification build on.\n1. See the Best Practices outlined in the SMART App Launch specification.\n1. See the [FHIR Security](https://www.hl7.org/fhir/security.html) section of the FHIR specification for requirements and recommendations.\n1. A server **SHALL** reject any unauthorized requests by returning an HTTP `401 Unauthorized`, `403 Forbidden`, or `404 Not Found` response code."
      }
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.