ÚNICAS Rare Diseases HL7 FHIR Implementation Guide
0.0.2 - draft

ÚNICAS Rare Diseases HL7 FHIR Implementation Guide - Local Development build (v0.0.2) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: Binary Documento en Base64 ÚNICAS

Official URL: https://unicas-fhir.sanidad.gob.es/StructureDefinition/UNICASBinary Version: 0.0.2
Draft as of 2025-11-10 Computable Name: UNICASBinary

Este profile define las restricciones del recurso Binary para representar el dato en base64 del documento clínico (HL7 CDA o PDF) en el contexto del caso de uso de ÚNICAS.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Binary 0..* Binary Pure binary content defined by a format other than FHIR
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contentType Σ 1..1 code Tipo de datos (application/pdf | multipart/x-hl7-cda-level-one)
Binding: MimeTypes (required): The mime type of an attachment. Any valid mime type is allowed.
... data 1..1 base64Binary Datos en base64 (Debe indicar un HL7 CDA o un PDF convertido a datos base64)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Binary.contentType Base required Mime Types 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())

This structure is derived from Binary

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Binary 0..* Binary Pure binary content defined by a format other than FHIR
... contentType 1..1 code Tipo de datos (application/pdf | multipart/x-hl7-cda-level-one)
... data 1..1 base64Binary Datos en base64 (Debe indicar un HL7 CDA o un PDF convertido a datos base64)

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Binary 0..* Binary Pure binary content defined by a format other than FHIR
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contentType Σ 1..1 code Tipo de datos (application/pdf | multipart/x-hl7-cda-level-one)
Binding: MimeTypes (required): The mime type of an attachment. Any valid mime type is allowed.
... securityContext Σ 0..1 Reference(Resource) Identifies another resource to use as proxy when enforcing access control
... data 1..1 base64Binary Datos en base64 (Debe indicar un HL7 CDA o un PDF convertido a datos base64)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Binary.language Base required All Languages 📍5.0.0 FHIR Std.
Binary.contentType Base required Mime Types 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())

This structure is derived from Binary

Summary

Mandatory: 1 element

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Binary 0..* Binary Pure binary content defined by a format other than FHIR
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contentType Σ 1..1 code Tipo de datos (application/pdf | multipart/x-hl7-cda-level-one)
Binding: MimeTypes (required): The mime type of an attachment. Any valid mime type is allowed.
... data 1..1 base64Binary Datos en base64 (Debe indicar un HL7 CDA o un PDF convertido a datos base64)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Binary.contentType Base required Mime Types 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())

Differential View

This structure is derived from Binary

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Binary 0..* Binary Pure binary content defined by a format other than FHIR
... contentType 1..1 code Tipo de datos (application/pdf | multipart/x-hl7-cda-level-one)
... data 1..1 base64Binary Datos en base64 (Debe indicar un HL7 CDA o un PDF convertido a datos base64)

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Binary 0..* Binary Pure binary content defined by a format other than FHIR
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... contentType Σ 1..1 code Tipo de datos (application/pdf | multipart/x-hl7-cda-level-one)
Binding: MimeTypes (required): The mime type of an attachment. Any valid mime type is allowed.
... securityContext Σ 0..1 Reference(Resource) Identifies another resource to use as proxy when enforcing access control
... data 1..1 base64Binary Datos en base64 (Debe indicar un HL7 CDA o un PDF convertido a datos base64)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Binary.language Base required All Languages 📍5.0.0 FHIR Std.
Binary.contentType Base required Mime Types 📍5.0.0 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())

This structure is derived from Binary

Summary

Mandatory: 1 element

 

Other representations of profile: CSV, Excel, Schematron

ÚNICAS está impulsado por el Consejo Interterritorial del Sistema Nacional de Salud, y financiado con fondos Next Generation de la Unión Europea, en el marco del Plan de Recuperación, Transformación y Resiliencia del Gobierno de España. El Ministerio de Sanidad ejerce la coordinación del proyecto, y Cataluña lidera la parte del desarrollo de los activos tecnológicos para su implementación.