/** * FHIR Version R5 * The following is auto generated resource definition. * * OpenAPI spec version: 3.0.1 * * * NOTE: This class is auto generated by the swagger code generator program. * https://github.com/swagger-api/swagger-codegen.git * Do not edit the class manually. */ import { Code } from './code'; import { CodeableConcept } from './codeableConcept'; import { CodeableReference } from './codeableReference'; import { DocumentReferenceAttester } from './documentReferenceAttester'; import { DocumentReferenceContent } from './documentReferenceContent'; import { DocumentReferenceRelatesTo } from './documentReferenceRelatesTo'; import { Extension } from './extension'; import { Id } from './id'; import { Identifier } from './identifier'; import { Instant } from './instant'; import { Markdown } from './markdown'; import { Meta } from './meta'; import { Narrative } from './narrative'; import { Period } from './period'; import { Reference } from './reference'; import { ResourceList } from './resourceList'; import { Uri } from './uri'; /** * A reference to a document of any kind for any purpose. While the term “document” implies a more narrow focus, for this resource this \"document\" encompasses *any* serialized object with a mime-type, it includes formal patient-centric documents (CDA), clinical notes, scanned paper, non-patient specific documents like policy text, as well as a photo, video, or audio recording acquired or used in healthcare. The DocumentReference resource provides metadata about the document so that the document can be discovered and managed. The actual content may be inline base64 encoded data or provided by direct reference. */ export interface DocumentReference { /** * This is a DocumentReference resource */ resourceType: 'DocumentReference'; id?: Id; meta?: Meta; implicitRules?: Uri; language?: Code; text?: Narrative; /** * These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. */ contained?: Array; /** * May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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. */ extension?: Array; /** * May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). */ modifierExtension?: Array; /** * Other business identifiers associated with the document, including version independent identifiers. */ identifier?: Array; version?: string; /** * A procedure that is fulfilled in whole or in part by the creation of this media. */ basedOn?: Array; status?: Code; docStatus?: Code; /** * Imaging modality used. This may include both acquisition and non-acquisition modalities. */ modality?: Array; type?: CodeableConcept; /** * A categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. */ category?: Array; subject?: Reference; /** * Describes the clinical encounter or type of care that the document content is associated with. */ context?: Array; /** * This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a \"History and Physical Report\" in which the procedure being documented is necessarily a \"History and Physical\" act. */ event?: Array; /** * The anatomic structures included in the document. */ bodySite?: Array; facilityType?: CodeableConcept; practiceSetting?: CodeableConcept; period?: Period; date?: Instant; /** * Identifies who is responsible for adding the information to the document. */ author?: Array; /** * A participant who has authenticated the accuracy of the document. */ attester?: Array; custodian?: Reference; /** * Relationships that this document has with other document references that already exist. */ relatesTo?: Array; description?: Markdown; /** * A set of Security-Tag codes specifying the level of privacy/security of the Document found at DocumentReference.content.attachment.url. Note that DocumentReference.meta.security contains the security labels of the data elements in DocumentReference, while DocumentReference.securityLabel contains the security labels for the document the reference refers to. The distinction recognizes that the document may contain sensitive information, while the DocumentReference is metadata about the document and thus might not be as sensitive as the document. For example: a psychotherapy episode may contain highly sensitive information, while the metadata may simply indicate that some episode happened. */ securityLabel?: Array; /** * The document and format referenced. If there are multiple content element repetitions, these must all represent the same document in different format, or attachment metadata. */ content: Array; }