/** * 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 { Annotation } from './annotation'; import { Canonical } from './canonical'; import { Code } from './code'; import { CodeableConcept } from './codeableConcept'; import { CodeableReference } from './codeableReference'; import { DateTime } from './dateTime'; import { Extension } from './extension'; import { Id } from './id'; import { Identifier } from './identifier'; import { Meta } from './meta'; import { Narrative } from './narrative'; import { Period } from './period'; import { Quantity } from './quantity'; import { Range } from './range'; import { Ratio } from './ratio'; import { Reference } from './reference'; import { ResourceList } from './resourceList'; import { ServiceRequestOrderDetail } from './serviceRequestOrderDetail'; import { ServiceRequestPatientInstruction } from './serviceRequestPatientInstruction'; import { Timing } from './timing'; import { Uri } from './uri'; /** * A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. */ export interface ServiceRequest { /** * This is a ServiceRequest resource */ resourceType: 'ServiceRequest'; 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; /** * Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller. */ identifier?: Array; /** * The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. */ instantiatesCanonical?: Array; /** * The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. */ instantiatesUri?: Array; /** * Plan/proposal/order fulfilled by this request. */ basedOn?: Array; /** * The request takes the place of the referenced completed or terminated request(s). */ replaces?: Array; requisition?: Identifier; status?: Code; intent?: Code; /** * A code that classifies the service for searching, sorting and display purposes (e.g. \"Surgical Procedure\"). */ category?: Array; priority?: Code; doNotPerform?: boolean; code?: CodeableReference; /** * Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. */ orderDetail?: Array; quantityQuantity?: Quantity; quantityRatio?: Ratio; quantityRange?: Range; subject: Reference; /** * The actual focus of a service request when it is not the subject of record representing something or someone associated with the subject such as a spouse, parent, fetus, or donor. The focus of a service request could also be an existing condition, an intervention, the subject's diet, another service request on the subject, or a body structure such as tumor or implanted device. */ focus?: Array; encounter?: Reference; /** * The date/time at which the requested service should occur. */ occurrenceDateTime?: string; occurrencePeriod?: Period; occurrenceTiming?: Timing; /** * If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example \"pain\", \"on flare-up\", etc. */ asNeededBoolean?: boolean; asNeededCodeableConcept?: CodeableConcept; authoredOn?: Date; requester?: Reference; performerType?: CodeableConcept; /** * The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. */ performer?: Array; /** * The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. */ location?: Array; /** * An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`. */ reason?: Array; /** * Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service. */ insurance?: Array; /** * Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as \"ask at order entry questions (AOEs)\". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. */ supportingInfo?: Array; /** * One or more specimens that the laboratory procedure will use. */ specimen?: Array; /** * Anatomic location where the procedure should be performed. This is the target site. */ bodySite?: Array; bodyStructure?: Reference; /** * Any other notes and comments made about the service request. For example, internal billing notes. */ note?: Array; /** * Instructions in terms that are understood by the patient or consumer. */ patientInstruction?: Array; /** * Key events in the history of the request. */ relevantHistory?: Array; }