Implementierungsleitfaden ISiK-Basismodul (4.0.1)

ISiKBinary

Dieses Profil ermöglicht die Darstellung von FHIR-fremden Formaten (z.B. PDFs, Bilder, CDA) in ISiK Szenarien.

Motivation

Für FHIR-fremde Formate werden die Daten base64-codiert in der Binary-Ressource (in XML oder JSON) transportiert oder über die REST-API am Binary-Endpunkt in ihrem nativen Format bereitgestellt. Binary-Ressourcen werden von Attachment-Elementen in DocumentReference-Ressourcen verlinkt und damit in den Kontext anderer FHIR-Ressourcen (z.B. Patient und Encounter) gestellt.

Kompatibilität

Hinweise zu Inkompatibilitäten können über die Portalseite gemeldet werden.

Hinweis

Das ISIK-Binary-Profil ist nicht Bestandteil der Implementierung und des Bestätigungsverfahrens zum ISIK Basismodul. Das Profil ist Teil des ISIK Basismoduls, da es als übergreifend genutzte Ressource sowohl im Modul Terminplanung als auch im Modul Dokumentenaustausch implementiert werden muss.

Metadaten

Canonical	https://gematik.de/fhir/isik/StructureDefinition/ISiKBinary
Status	active
Version	4.0.1
Basis	http://hl7.org/fhir/StructureDefinition/Binary

Inhalt

ISiKBinary (Binary)			Binary	There are no (further) constraints on this element Element id Binary Short description Pure binary content defined by a format other than FHIR Definition A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc. Comments Typically, Binary resources are used for handling content such as: CDA Documents (i.e. with XDS) PDF Documents Images (the Media resource is preferred for handling images, but not possible when the content is already binary - e.g. XDS). Data type Binary Mappings rim: Entity. Role, or Act rim: ED
id	Σ	0..1	string	There are no (further) constraints on this element Element id Binary.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Binary.meta Short description Metadata about the resource Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Binary.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id Binary.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
contentType	S Σ	1..1	codeBinding	Element id Binary.contentType Short description MimeType der Binärdaten Definition MimeType of the binary content represented as a standard MimeType (BCP 13). Comments z.B. "application/pdf" oder "image/jpeg" Begründung Pflichtfeld: Ohne Kenntnis des MimeTypes sind die Base65-codierten Daten in `data` nicht interpretierbar Data type code Binding The mime type of an attachment. Any valid mime type is allowed. Mime Types (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: ED.mediaType
securityContext	Σ I	0..1	Reference(Resource)	There are no (further) constraints on this element Element id Binary.securityContext Short description Identifies another resource to use as proxy when enforcing access control Definition This element identifies another resource that can be used as a proxy of the security sensitivity to use when deciding and enforcing access control rules for the Binary resource. Given that the Binary resource contains very few elements that can be used to determine the sensitivity of the data and relationships to individuals, the referenced resource stands in as a proxy equivalent for this purpose. This referenced resource may be related to the Binary (e.g. Media, DocumentReference), or may be some non-related Resource purely as a security proxy. E.g. to identify that the binary resource relates to a patient, and access should only be granted to applications that have access to the patient. Comments Very often, a server will also know of a resource that references the binary, and can automatically apply the appropriate access rules based on that reference. However, there are some circumstances where this is not appropriate, e.g. the binary is uploaded directly to the server without any linking resource, the binary is referred to from multiple different resources, and/or the binary is content such as an application logo that has less protection than any of the resources that reference it. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
data	S	1..1	base64Binary	Element id Binary.data Short description Base64-codierte Binärdaten Definition The actual content, base64 encoded. Comments Begründung Pflichtfeld: Sind keine Binärdaten vorhanden, ist diese Ressource sinnlos. Data type base64Binary Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: ED.data

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="ISiKBinary" />
    <url value="https://gematik.de/fhir/isik/StructureDefinition/ISiKBinary" />
    <version value="4.0.1" />
    <name value="ISiKBinary" />
    <title value="ISiKBinary" />
    <status value="active" />
    <experimental value="false" />
    <date value="2024-11-25" />
    <publisher value="gematik GmbH" />
    <description value="Dieses Profil erm&#246;glicht die Darstellung von FHIR-fremden Formaten (z.B. PDFs, Bilder, CDA) in ISiK Szenarien. \n\n### Motivation\nF&#252;r FHIR-fremde Formate werden die Daten base64-codiert in der Binary-Ressource (in XML oder JSON) transportiert oder \n&#252;ber die REST-API am Binary-Endpunkt in ihrem nativen Format bereitgestellt. \nBinary-Ressourcen werden von Attachment-Elementen in DocumentReference-Ressourcen verlinkt und damit in den Kontext anderer FHIR-Ressourcen (z.B. Patient und Encounter) gestellt. \n\n### Kompatibilit&#228;t\n\nHinweise zu Inkompatibilit&#228;ten k&#246;nnen &#252;ber die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden.\n\n### Hinweis\n\nDas ISIK-Binary-Profil ist *nicht* Bestandteil der Implementierung und des Best&#228;tigungsverfahrens zum ISIK Basismodul.\nDas Profil ist Teil des ISIK Basismoduls, da es als &#252;bergreifend genutzte Ressource sowohl im [Modul Terminplanung](https://simplifier.net/guide/isik-terminplanung-v4/ImplementationGuide-markdown-Datenobjekte?version=current) als auch im [Modul Dokumentenaustausch](https://simplifier.net/guide/isik-dokumentenaustausch-v4/ImplementationGuide-markdown-Datenobjekte?version=current) implementiert werden muss." />
    <fhirVersion value="4.0.1" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="Binary" />
    <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Binary" />
    <derivation value="constraint" />
    <differential>
        <element id="Binary.contentType">
            <path value="Binary.contentType" />
            <short value="MimeType der Bin&#228;rdaten" />
            <comment value="z.B. &amp;quot;application/pdf&amp;quot; oder &amp;quot;image/jpeg&amp;quot;  \n    **Begr&#252;ndung Pflichtfeld:** Ohne Kenntnis des MimeTypes sind die Base65-codierten Daten in `data` nicht interpretierbar" />
            <mustSupport value="true" />
        </element>
        <element id="Binary.data">
            <path value="Binary.data" />
            <short value="Base64-codierte Bin&#228;rdaten" />
            <comment value="**Begr&#252;ndung Pflichtfeld:** Sind keine Bin&#228;rdaten vorhanden, ist diese Ressource sinnlos." />
            <min value="1" />
            <mustSupport value="true" />
        </element>
    </differential>
</StructureDefinition>

{
    "resourceType": "StructureDefinition",
    "id": "ISiKBinary",
    "url": "https://gematik.de/fhir/isik/StructureDefinition/ISiKBinary",
    "version": "4.0.1",
    "name": "ISiKBinary",
    "title": "ISiKBinary",
    "status": "active",
    "experimental": false,
    "date": "2024-11-25",
    "publisher": "gematik GmbH",
    "description": "Dieses Profil ermöglicht die Darstellung von FHIR-fremden Formaten (z.B. PDFs, Bilder, CDA) in ISiK Szenarien. \n\n### Motivation\nFür FHIR-fremde Formate werden die Daten base64-codiert in der Binary-Ressource (in XML oder JSON) transportiert oder \nüber die REST-API am Binary-Endpunkt in ihrem nativen Format bereitgestellt. \nBinary-Ressourcen werden von Attachment-Elementen in DocumentReference-Ressourcen verlinkt und damit in den Kontext anderer FHIR-Ressourcen (z.B. Patient und Encounter) gestellt. \n\n### Kompatibilität\n\nHinweise zu Inkompatibilitäten können über die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden.\n\n### Hinweis\n\nDas ISIK-Binary-Profil ist *nicht* Bestandteil der Implementierung und des Bestätigungsverfahrens zum ISIK Basismodul.\nDas Profil ist Teil des ISIK Basismoduls, da es als übergreifend genutzte Ressource sowohl im [Modul Terminplanung](https://simplifier.net/guide/isik-terminplanung-v4/ImplementationGuide-markdown-Datenobjekte?version=current) als auch im [Modul Dokumentenaustausch](https://simplifier.net/guide/isik-dokumentenaustausch-v4/ImplementationGuide-markdown-Datenobjekte?version=current) implementiert werden muss.  ",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "Binary",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Binary",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "Binary.contentType",
                "path": "Binary.contentType",
                "short": "MimeType der Binärdaten",
                "comment": "z.B. &quot;application/pdf&quot; oder &quot;image/jpeg&quot;  \n    **Begründung Pflichtfeld:** Ohne Kenntnis des MimeTypes sind die Base65-codierten Daten in `data` nicht interpretierbar",
                "mustSupport": true
            },
            {
                "id": "Binary.data",
                "path": "Binary.data",
                "short": "Base64-codierte Binärdaten",
                "comment": "**Begründung Pflichtfeld:** Sind keine Binärdaten vorhanden, ist diese Ressource sinnlos.",
                "min": 1,
                "mustSupport": true
            }
        ]
    }
}

ISiKBinary

ISiKBinary

Motivation

Kompatibilität

Hinweis

Metadaten

Inhalt

Constraints/Invarianten