| Type | Reference | Content |
|---|---|---|
| web | www.hl7.dk |
|
| web | github.com | Danish Implementation Guide for SMART App Launch, published by HL7 Denmark. This guide is not an authorized publication; it is the continuous build for version 1.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7dk/dk-smart/ and changes regularly. See the Directory of published versions |
| web | www.hl7.dk |
IG © 2024+ HL7 Denmark
. Package hl7.fhir.dk.smart#1.1.0 based on FHIR 4.0.1
. Generated 2025-03-14
Links: Table of Contents | QA Report| 
| Source
| Propose a change
|
| web | raw.githubusercontent.com |
Links: Table of Contents
| QA Report
|
| Source
| Propose a change
|
| web | github.com |
Links: Table of Contents
| QA Report
|
| Source
| Propose a change
|
| web | github.com |
Links: Table of Contents
| QA Report
|
| Source
| Propose a change
|
| web | hl7.dk | The Danish SMART Server Capability Statement definition includes formal requirements for SMART servers in Denmark. In essence, it mandates support for REST API's and for JSON format, and recommends support for the IPA specification and for XML format. The Danish SMART Server Capability Statement Profile is intended to help in validation of server capability statements. It is expected that servers supporting SMART also serves FHIR resources that complies with those listed in DK Core (where applicable). |
| web | oauth.net | Please do not implement the SMART App Launch mechanism based on examples! Examples in this implementation guide are meant to offer additional clarity on how the SMART App Launch mechanism works in certain circumstances. However, to appreciate all the details of the security mechanisms involved, all implementers of the SMART App Launch mechanism really need to study and understand the main SMART App Launch specification , and the underlying OAuth2 and OpenID Connect specifications. Do give information security the attention it deserves! |
| web | openid.net | Please do not implement the SMART App Launch mechanism based on examples! Examples in this implementation guide are meant to offer additional clarity on how the SMART App Launch mechanism works in certain circumstances. However, to appreciate all the details of the security mechanisms involved, all implementers of the SMART App Launch mechanism really need to study and understand the main SMART App Launch specification , and the underlying OAuth2 and OpenID Connect specifications. Do give information security the attention it deserves! |
| web | hl7.dk | There is a separate implementation guide for Danish Core Profiles that defines the Danish Core profiles for some of the key FHIR resources. |
| web | hl7.dk | We have DK Core . That defines the FHIR models in a danish perspective |
| web | hl7.dk | We have support of the IPA model parts in DK Core (from v3.4.0) but deliberately not the SMART parts in DK Core . |
| web | hl7.dk | So, when we pair DK Core (with the danish models) and DK SMART (which outlines standardized access) we end up with a standardized way of expressing the data model and the data access which is the core essence of bridging systems and break down silos. This inherently supports initiatives like https://medcom.dk/projekter/apps-i-almen-praksis/ and boards like https://laegemiddelstyrelsen.dk/da/udstyr/naevnet-for-sundhedsapps/ |
| web | medcom.dk | So, when we pair DK Core (with the danish models) and DK SMART (which outlines standardized access) we end up with a standardized way of expressing the data model and the data access which is the core essence of bridging systems and break down silos. This inherently supports initiatives like https://medcom.dk/projekter/apps-i-almen-praksis/ and boards like https://laegemiddelstyrelsen.dk/da/udstyr/naevnet-for-sundhedsapps/ |
| web | laegemiddelstyrelsen.dk | So, when we pair DK Core (with the danish models) and DK SMART (which outlines standardized access) we end up with a standardized way of expressing the data model and the data access which is the core essence of bridging systems and break down silos. This inherently supports initiatives like https://medcom.dk/projekter/apps-i-almen-praksis/ and boards like https://laegemiddelstyrelsen.dk/da/udstyr/naevnet-for-sundhedsapps/ |
| web | www.mitid.dk | National existing solutions like MitID and SEB as well as any local SAML-based solution can be incorporated into using SMART -flows for the authentication/authorization-parts adding value to the entire chain. The use of SMART does not compromise that. It only strengthens is. |
| web | services.nsi.dk | National existing solutions like MitID and SEB as well as any local SAML-based solution can be incorporated into using SMART -flows for the authentication/authorization-parts adding value to the entire chain. The use of SMART does not compromise that. It only strengthens is. |
| web | en.wikipedia.org | National existing solutions like MitID and SEB as well as any local SAML-based solution can be incorporated into using SMART -flows for the authentication/authorization-parts adding value to the entire chain. The use of SMART does not compromise that. It only strengthens is. |
| web | hl7.fi | See the Finnish progress here |
| web | www.hl7.dk | To learn about the current status in Denmark, please contact HL7 Denmark . We're happy to give you an overview. |
| web | www.hl7.dk | The profiling work is performed in a project driven by HL7 Denmark . See the announcement and the running european memo . We warmly welcome new participants to the project. |
| web | docs.google.com | The profiling work is performed in a project driven by HL7 Denmark . See the announcement and the running european memo . We warmly welcome new participants to the project. |
| web | www.nspop.dk | Any vendor providing access to data (not limited to, but including using SMART ) MUST remember that access to such provided data in many cases are subject to be sent to MinLog . |
| web | github.com | The source code of this implementation guide is maintained in a publicly accessible repository in GitHub. Issues opened in that GitHub repo are very welcome. They help the team pick up any proposed changes or additions and to discuss them publicly. |
| web | creativecommons.org | This document is licensed under Creative Commons CC0 1.0 Universal Public Domain Dedication. |
| web | www.iso.org |
ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage
|