Skip to main content

Attachment

For referring to data content defined in other formats. If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions

type Attachment implements Element {
  contentType: String
  language: String
  data: String
  url: Uri
  size: Int
  hash: String
  title: String
  creation: Date
  extension: [Extension]
  id: String
}

Fields​

Attachment.contentType ● String scalar​

Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.

Attachment.language ● String scalar​

The human language of the content. The value can be any valid value according to BCP 47.

Attachment.data ● String scalar​

The actual data of the attachment - a sequence of bytes, base64 encoded.

Attachment.url ● Uri scalar​

A location where the data can be accessed.

Attachment.size ● Int scalar​

The number of bytes of data that make up this attachment (before base64 encoding, if that is done).

Attachment.hash ● String scalar​

The calculated hash of the data using SHA-1. Represented using base64.

Attachment.title ● String scalar​

A label or set of text to display in place of the data.

Attachment.creation ● Date scalar​

The date that the attachment was first created.

Attachment.extension ● [Extension] list object​

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Attachment.id ● String scalar​

Interfaces​

Element interface​

Base definition for all elements in a resource. If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions

Member Of​

AdministrableProductDefinitionProperty object ● BodyStructure object ● CitationRelatesTo object ● CitationRelatesTo1 object ● ClaimResponse object ● ClaimSupportingInfo object ● CommunicationPayload object ● CommunicationRequestPayload object ● Consent object ● Contract object ● ContractAnswer object ● ContractFriendly object ● ContractLegal object ● ContractRule object ● DiagnosticReport object ● DocumentReferenceContent object ● ElementDefinition object ● ElementDefinitionExample object ● ExplanationOfBenefit object ● ExplanationOfBenefitSupportingInfo object ● Extension object ● HealthcareService object ● Library object ● ManufacturedItemDefinitionProperty object ● Media object ● MedicinalProductDefinitionCharacteristic object ● NutritionProductProductCharacteristic object ● PackagedProductDefinitionProperty object ● Patient object ● Person object ● Practitioner object ● ProdCharacteristic object ● QuestionnaireInitial object ● QuestionnaireResponseAnswer object ● RelatedArtifact object ● RelatedPerson object ● StructureMapSource object ● SubstanceDefinitionProperty object ● TaskInput object ● TaskOutput object