ReteLabBinaryDocumento

ReteLabBinaryDocumento
- Descrizione
- ValueSet

Descrizione

Il profilo ReteLabBinaryDocumento è stato strutturato a partire dalla risorsa generica FHIR Binary utilizzata per descrivere il documento PDF:

"Note di accompagnamento" allegato alla richiesta,
"Etichetta" allegato al campione.

Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: ReteLabBinaryDocumento.

Snapshot View

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
contentType	Σ	1..1	codeBinding	There are no (further) constraints on this element Element Id Binary.contentType Short description MimeType of the binary content Definition MimeType of the binary content represented as a standard MimeType (BCP 13). Comments Note that FHIR strings SHALL NOT exceed 1MB in size 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		0..1	base64Binary	Element Id Binary.data Short description Il documento codificato Base64 Definition The actual content, base64 encoded. Comments Corrispondente al campo HL7 OBX-5.5 per la nota di accompagnamento Corrispondente al campo HL7 ZBX-3.5 per le etichette 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
contentType			Fixed Value	There are no (further) constraints on this element Element Id Binary.contentType Short description Fisso, documento pdf Fixed Value application/pdf

Differential View

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
contentType	Σ	1..1	codeBinding	There are no (further) constraints on this element Element Id Binary.contentType Short description MimeType of the binary content Definition MimeType of the binary content represented as a standard MimeType (BCP 13). Comments Note that FHIR strings SHALL NOT exceed 1MB in size 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		0..1	base64Binary	Element Id Binary.data Short description Il documento codificato Base64 Definition The actual content, base64 encoded. Comments Corrispondente al campo HL7 OBX-5.5 per la nota di accompagnamento Corrispondente al campo HL7 ZBX-3.5 per le etichette 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
contentType			Fixed Value	There are no (further) constraints on this element Element Id Binary.contentType Short description Fisso, documento pdf Fixed Value application/pdf

Hybrid View

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
contentType	Σ	1..1	codeBinding	There are no (further) constraints on this element Element Id Binary.contentType Short description MimeType of the binary content Definition MimeType of the binary content represented as a standard MimeType (BCP 13). Comments Note that FHIR strings SHALL NOT exceed 1MB in size 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		0..1	base64Binary	Element Id Binary.data Short description Il documento codificato Base64 Definition The actual content, base64 encoded. Comments Corrispondente al campo HL7 OBX-5.5 per la nota di accompagnamento Corrispondente al campo HL7 ZBX-3.5 per le etichette 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
contentType			Fixed Value	There are no (further) constraints on this element Element Id Binary.contentType Short description Fisso, documento pdf Fixed Value application/pdf

Table View

Binary		..
Binary.data		..
Binary.contentType		..

XML View

<StructureDefinition xmlns="http://hl7.org/fhir">
    <url value="https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabBinaryDocumentoPDFEncodedBase64" />
    <name value="ReteLabBinaryDocumento" />
    <status value="active" />
    <date value="2023-12-21T14:31:53.6384566+00:00" />
    <description value="Profilo volto a descrivere il documento PDF:\n- &quot;Note di accompagnamento&quot; allegato alla richiesta.\n- &quot;Etichetta&quot; allegato al campione" />
    <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.data">
            <path value="Binary.data" />
            <short value="Il documento codificato Base64" />
            <comment value="Corrispondente al campo HL7 OBX-5.5 per la nota di accompagnamento\nCorrispondente al campo HL7 ZBX-3.5 per le etichette" />
        </element>
        <element id="Binary.contentType">
            <path value="Binary.contentType" />
            <short value="Fisso, documento pdf" />
            <fixedCode value="application/pdf" />
        </element>
    </differential>
</StructureDefinition>

JSON View

{
    "resourceType": "StructureDefinition",
    "url": "https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabBinaryDocumentoPDFEncodedBase64",
    "name": "ReteLabBinaryDocumento",
    "status": "active",
    "date": "2023-12-21T14:31:53.6384566+00:00",
    "description": "Profilo volto a descrivere il documento PDF:\n- \"Note di accompagnamento\" allegato alla richiesta.\n- \"Etichetta\" allegato al campione",
    "fhirVersion": "4.0.1",
    "kind": "resource",
    "abstract": false,
    "type": "Binary",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Binary",
    "derivation": "constraint",
    "differential": {
        "element":  [
            {
                "id": "Binary.data",
                "path": "Binary.data",
                "short": "Il documento codificato Base64",
                "comment": "Corrispondente al campo HL7 OBX-5.5 per la nota di accompagnamento\nCorrispondente al campo HL7 ZBX-3.5 per le etichette"
            },
            {
                "id": "Binary.contentType",
                "path": "Binary.contentType",
                "short": "Fisso, documento pdf",
                "fixedCode": "application/pdf"
            }
        ]
    }
}

Esempi

esempio-binary-notadiaccompagnamento

esempio-binary-etichettePDF

ValueSet

Attualmente non sono definiti value set specifici per il profilo ReteLabBinaryDocumento.