FHIR © HL7.org  |  Server Home  |  XIG Home  |  Server Source  |  FHIR  

FHIR IG Statistics: CapabilityStatement/dk-smart-server

Packagehl7.fhir.dk.smart
TypeCapabilityStatement
Iddk-smart-server
FHIR VersionR4
Sourcehttp://hl7.dk/fhir/smart/http://hl7.dk/fhir/smart/1.0.0/CapabilityStatement-dk-smart-server.html
URLhttp://hl7.dk/fhir/smart/CapabilityStatement/dk-smart-server
Version1.0.0
Statusactive
Date2023-11-09
NameDKSmartServer
TitleDanish SMART Server Capability Statement
Realmdk
Authorityhl7
DescriptionThis CapabilityStatement describes the basic rules for a server actor providing SMART App Launch in Denmark.
Kindrequirements

Resources that use this resource

No resources found


Resources that this resource uses

ImplementationGuide
hl7.fhir.uv.ipaInternational Patient Access
hl7.fhir.uv.smart-app-launchSMART App Launch

Narrative

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

Generated Narrative: CapabilityStatement dk-smart-server

Danish SMART Server Capability Statement

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

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": "dk-smart-server",
  "text": {
    "status": "extensions",
    "div": "<!-- snip (see above) -->"
  },
  "url": "http://hl7.dk/fhir/smart/CapabilityStatement/dk-smart-server",
  "version": "1.0.0",
  "name": "DKSmartServer",
  "title": "Danish SMART Server Capability Statement",
  "status": "active",
  "date": "2023-11-09",
  "publisher": "HL7 Denmark",
  "contact": [
    {
      "name": "HL7 Denmark",
      "telecom": [
        {
          "system": "url",
          "value": "https://www.hl7.dk/"
        },
        {
          "system": "email",
          "value": "jenskristianvilladsen@gmail.com"
        }
      ]
    }
  ],
  "description": "This CapabilityStatement describes the basic rules for a server actor providing SMART App Launch in Denmark.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "urn:iso:std:iso:3166",
          "code": "DK",
          "display": "Denmark"
        }
      ]
    }
  ],
  "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."
      }
    }
  ]
}