FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R5.ExampleScenarioResourceType for use in FHIR R4

Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-examplescenario-instance-type-for-R4 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 1 Computable Name: R5_examplescenario_instance_type_for_R4

This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/examplescenario-instance-type 5.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://hl7.org/fhir/fhir-types version 5.0.0
    CodeDisplayDefinition
    AccountAccountA financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc.
    ActivityDefinitionActivityDefinitionThis resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.
    ActorDefinitionActorDefinitionThe ActorDefinition resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays.
    AdministrableProductDefinitionAdministrableProductDefinitionA medicinal product in the final form which is suitable for administering to a patient (after any mixing of multiple components, dissolution etc. has been performed).
    AdverseEventAdverseEventAn event (i.e. any change to current patient status) that may be related to unintended effects on a patient or research participant. The unintended effects may require additional monitoring, treatment, hospitalization, or may result in death. The AdverseEvent resource also extends to potential or avoided events that could have had such effects. There are two major domains where the AdverseEvent resource is expected to be used. One is in clinical care reported adverse events and the other is in reporting adverse events in clinical research trial management. Adverse events can be reported by healthcare providers, patients, caregivers or by medical products manufacturers. Given the differences between these two concepts, we recommend consulting the domain specific implementation guides when implementing the AdverseEvent Resource. The implementation guides include specific extensions, value sets and constraints.
    AllergyIntoleranceAllergyIntoleranceRisk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance.
    AppointmentAppointmentA booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).
    AppointmentResponseAppointmentResponseA reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection.
    ArtifactAssessmentArtifactAssessmentThis Resource provides one or more comments, classifiers or ratings about a Resource and supports attribution and rights management metadata for the added content.
    AuditEventAuditEventA record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis.
    BasicBasicBasic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.
    BinaryBinaryA 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.
    BiologicallyDerivedProductBiologicallyDerivedProductA biological material originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.
    BiologicallyDerivedProductDispenseBiologicallyDerivedProductDispenseA record of dispensation of a biologically derived product.
    BodyStructureBodyStructureRecord details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.
    BundleBundleA container for a collection of resources.
    CapabilityStatementCapabilityStatementA Capability Statement documents a set of capabilities (behaviors) of a FHIR Server or Client for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
    CarePlanCarePlanDescribes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.
    CareTeamCareTeamThe Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care.
    ChargeItemChargeItemThe resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation.
    ChargeItemDefinitionChargeItemDefinitionThe ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system.
    CitationCitationThe Citation Resource enables reference to any knowledge artifact for purposes of identification and attribution. The Citation Resource supports existing reference structures and developing publication practices such as versioning, expressing complex contributorship roles, and referencing computable resources.
    ClaimClaimA provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement.
    ClaimResponseClaimResponseThis resource provides the adjudication details from the processing of a Claim resource.
    ClinicalImpressionClinicalImpressionA record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with the recording of assessment tools such as Apgar score.
    ClinicalUseDefinitionClinicalUseDefinitionA single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.
    CodeSystemCodeSystemThe CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content.
    CommunicationCommunicationA clinical or business level record of information being transmitted or shared; e.g. an alert that was sent to a responsible provider, a public health agency communication to a provider/reporter in response to a case report for a reportable condition.
    CommunicationRequestCommunicationRequestA request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition.
    CompartmentDefinitionCompartmentDefinitionA compartment definition that defines how resources are accessed on a server.
    CompositionCompositionA set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).
    ConceptMapConceptMapA statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models.
    ConditionConditionA clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
    ConditionDefinitionConditionDefinitionA definition of a condition and information relevant to managing it.
    ConsentConsentA record of a healthcare consumer’s choices or choices made on their behalf by a third party, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
    ContractContractLegally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement.
    CoverageCoverageFinancial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.
    CoverageEligibilityRequestCoverageEligibilityRequestThe CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy.
    CoverageEligibilityResponseCoverageEligibilityResponseThis resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource.
    DetectedIssueDetectedIssueIndicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, gaps in care, etc.
    DeviceDeviceThis resource describes the properties (regulated, has real time clock, etc.), adminstrative (manufacturer name, model number, serial number, firmware, etc.), and type (knee replacement, blood pressure cuff, MRI, etc.) of a physical unit (these values do not change much within a given module, for example the serail number, manufacturer name, and model number). An actual unit may consist of several modules in a distinct hierarchy and these are represented by multiple Device resources and bound through the 'parent' element.
    DeviceAssociationDeviceAssociationA record of association of a device.
    DeviceDefinitionDeviceDefinitionThis is a specialized resource that defines the characteristics and capabilities of a device.
    DeviceDispenseDeviceDispenseIndicates that a device is to be or has been dispensed for a named person/patient. This includes a description of the product (supply) provided and the instructions for using the device.
    DeviceMetricDeviceMetricDescribes a measurement, calculation or setting capability of a device. The DeviceMetric resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable.
    DeviceRequestDeviceRequestRepresents a request a device to be provided to a specific patient. The device may be an implantable device to be subsequently implanted, or an external assistive device, such as a walker, to be delivered and subsequently be used.
    DeviceUsageDeviceUsageA record of a device being used by a patient where the record is the result of a report from the patient or a clinician.
    DiagnosticReportDiagnosticReportThe findings and interpretation of diagnostic tests performed on patients, groups of patients, products, substances, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. The report also includes non-clinical context such as batch analysis and stability reporting of products and substances.
    DocumentReferenceDocumentReferenceA 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.
    EncounterEncounterAn interaction between healthcare provider(s), and/or patient(s) for the purpose of providing healthcare service(s) or assessing the health status of patient(s).
    EncounterHistoryEncounterHistoryA record of significant events/milestones key data throughout the history of an Encounter
    EndpointEndpointThe technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b, a REST endpoint for another FHIR server, or a s/Mime email address. This may include any security context information.
    EnrollmentRequestEnrollmentRequestThis resource provides the insurance enrollment details to the insurer regarding a specified coverage.
    EnrollmentResponseEnrollmentResponseThis resource provides enrollment and plan details from the processing of an EnrollmentRequest resource.
    EpisodeOfCareEpisodeOfCareAn association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time.
    EventDefinitionEventDefinitionThe EventDefinition resource provides a reusable description of when a particular event can occur.
    EvidenceEvidenceThe Evidence Resource provides a machine-interpretable expression of an evidence concept including the evidence variables (e.g., population, exposures/interventions, comparators, outcomes, measured variables, confounding variables), the statistics, and the certainty of this evidence.
    EvidenceReportEvidenceReportThe EvidenceReport Resource is a specialized container for a collection of resources and codeable concepts, adapted to support compositions of Evidence, EvidenceVariable, and Citation resources and related concepts.
    EvidenceVariableEvidenceVariableThe EvidenceVariable resource describes an element that knowledge (Evidence) is about.
    ExampleScenarioExampleScenarioA walkthrough of a workflow showing the interaction between systems and the instances shared, possibly including the evolution of instances over time.
    ExplanationOfBenefitExplanationOfBenefitThis resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided.
    FamilyMemberHistoryFamilyMemberHistorySignificant health conditions for a person related to the patient relevant in the context of care for the patient.
    FlagFlagProspective warnings of potential issues when providing care to the patient.
    FormularyItemFormularyItemThis resource describes a product or service that is available through a program and includes the conditions and constraints of availability. All of the information in this resource is specific to the inclusion of the item in the formulary and is not inherent to the item itself.
    GenomicStudyGenomicStudyA set of analyses performed to analyze and generate genomic data.
    GoalGoalDescribes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.
    GraphDefinitionGraphDefinitionA formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set.
    GroupGroupRepresents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization.
    GuidanceResponseGuidanceResponseA guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken.
    HealthcareServiceHealthcareServiceThe details of a healthcare service available at a location or in a catalog. In the case where there is a hierarchy of services (for example, Lab -> Pathology -> Wound Cultures), this can be represented using a set of linked HealthcareServices.
    ImagingSelectionImagingSelectionA selection of DICOM SOP instances and/or frames within a single Study and Series. This might include additional specifics such as an image region, an Observation UID or a Segmentation Number, allowing linkage to an Observation Resource or transferring this information along with the ImagingStudy Resource.
    ImagingStudyImagingStudyRepresentation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities.
    ImmunizationImmunizationDescribes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.
    ImmunizationEvaluationImmunizationEvaluationDescribes a comparison of an immunization event against published recommendations to determine if the administration is "valid" in relation to those recommendations.
    ImmunizationRecommendationImmunizationRecommendationA patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification.
    ImplementationGuideImplementationGuideA set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts.
    IngredientIngredientAn ingredient of a manufactured item or pharmaceutical product.
    InsurancePlanInsurancePlanDetails of a Health Insurance product/plan provided by an organization.
    InventoryItemInventoryItemfunctional description of an inventory item used in inventory and supply-related workflows.
    InventoryReportInventoryReportA report of inventory or stock items.
    InvoiceInvoiceInvoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.
    LibraryLibraryThe Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose existing knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets.
    LinkageLinkageIdentifies two or more records (resource instances) that refer to the same real-world "occurrence".
    ListListA List is a curated collection of resources, for things such as problem lists, allergy lists, facility list, organization list, etc.
    LocationLocationDetails and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.
    ManufacturedItemDefinitionManufacturedItemDefinitionThe definition and characteristics of a medicinal manufactured item, such as a tablet or capsule, as contained in a packaged medicinal product.
    MeasureMeasureThe Measure resource provides the definition of a quality measure.
    MeasureReportMeasureReportThe MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation.
    MedicationMedicationThis resource is primarily used for the identification and definition of a medication, including ingredients, for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.
    MedicationAdministrationMedicationAdministrationDescribes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. This event can also be used to record waste using a status of not-done and the appropriate statusReason.
    MedicationDispenseMedicationDispenseIndicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.
    MedicationKnowledgeMedicationKnowledgeInformation about a medication that is used to support knowledge.
    MedicationRequestMedicationRequestAn order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
    MedicationStatementMedicationStatementA record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains.

    The primary difference between a medicationstatement and a medicationadministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medicationstatement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the Medication Statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information.
    MedicinalProductDefinitionMedicinalProductDefinitionDetailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use, drug catalogs, to support prescribing, adverse events management etc.).
    MessageDefinitionMessageDefinitionDefines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted.
    MessageHeaderMessageHeaderThe header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
    MolecularSequenceMolecularSequenceRepresentation of a molecular sequence.
    NamingSystemNamingSystemA curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types.
    NutritionIntakeNutritionIntakeA record of food or fluid that is being consumed by a patient. A NutritionIntake may indicate that the patient may be consuming the food or fluid now or has consumed the food or fluid in the past. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay or through an app that tracks food or fluids consumed. The consumption information may come from sources such as the patient's memory, from a nutrition label, or from a clinician documenting observed intake.
    NutritionOrderNutritionOrderA request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident.
    NutritionProductNutritionProductA food or supplement that is consumed by patients.
    ObservationObservationMeasurements and simple assertions made about a patient, device or other subject.
    ObservationDefinitionObservationDefinitionSet of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service.
    OperationDefinitionOperationDefinitionA formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).
    OperationOutcomeOperationOutcomeA collection of error, warning, or information messages that result from a system action.
    OrganizationOrganizationA formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.
    OrganizationAffiliationOrganizationAffiliationDefines an affiliation/assotiation/relationship between 2 distinct organizations, that is not a part-of relationship/sub-division relationship.
    PackagedProductDefinitionPackagedProductDefinitionA medically related item or items, in a container or package.
    ParametersParametersThis resource is used to pass information into and back from an operation (whether invoked directly from REST or within a messaging environment). It is not persisted or allowed to be referenced by other resources except as described in the definition of the Parameters resource.
    PatientPatientDemographics and other administrative information about an individual or animal receiving care or other health-related services.
    PaymentNoticePaymentNoticeThis resource provides the status of the payment for goods and services rendered, and the request and response resource references.
    PaymentReconciliationPaymentReconciliationThis resource provides the details including amount of a payment and allocates the payment items being paid.
    PermissionPermissionPermission resource holds access rules for a given data and context.
    PersonPersonDemographics and administrative information about a person independent of a specific health-related context.
    PlanDefinitionPlanDefinitionThis resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical and non-clinical artifacts such as clinical decision support rules, order sets, protocols, and drug quality specifications.
    PractitionerPractitionerA person who is directly or indirectly involved in the provisioning of healthcare or related services.
    PractitionerRolePractitionerRoleA specific set of Roles/Locations/specialties/services that a practitioner may perform, or has performed at an organization during a period of time.
    ProcedureProcedureAn action that is or was performed on or for a patient, practitioner, device, organization, or location. For example, this can be a physical intervention on a patient like an operation, or less invasive like long term services, counseling, or hypnotherapy. This can be a quality or safety inspection for a location, organization, or device. This can be an accreditation procedure on a practitioner for licensing.
    ProvenanceProvenanceProvenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies.
    QuestionnaireQuestionnaireA structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.
    QuestionnaireResponseQuestionnaireResponseA structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to.
    RegulatedAuthorizationRegulatedAuthorizationRegulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity that is cited in a guidance, regulation, rule or legislative act. An example is Market Authorization relating to a Medicinal Product.
    RelatedPersonRelatedPersonInformation about a person that is involved in a patient's health or the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.
    RequestOrchestrationRequestOrchestrationA set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one".
    RequirementsRequirementsThe Requirements resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays.
    ResearchStudyResearchStudyA scientific study of nature that sometimes includes processes involved in health and disease. For example, clinical trials are research studies that involve people. These studies may be related to new ways to screen, prevent, diagnose, and treat disease. They may also study certain outcomes and certain groups of people by looking at data collected in the past or future.
    ResearchSubjectResearchSubjectA ResearchSubject is a participant or object which is the recipient of investigative activities in a research study.
    RiskAssessmentRiskAssessmentAn assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome.
    ScheduleScheduleA container for slots of time that may be available for booking appointments.
    SearchParameterSearchParameterA search parameter that defines a named search item that can be used to search/filter on a resource.
    ServiceRequestServiceRequestA record of a request for service such as diagnostic investigations, treatments, or operations to be performed.
    SlotSlotA slot of time on a schedule that may be available for booking appointments.
    SpecimenSpecimenA sample to be used for analysis.
    SpecimenDefinitionSpecimenDefinitionA kind of specimen with associated set of requirements.
    StructureDefinitionStructureDefinitionA definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types.
    StructureMapStructureMapA Map of relationships between 2 structures that can be used to transform data.
    SubscriptionSubscriptionThe subscription resource describes a particular client's request to be notified about a SubscriptionTopic.
    SubscriptionStatusSubscriptionStatusThe SubscriptionStatus resource describes the state of a Subscription during notifications. It is not persisted.
    SubscriptionTopicSubscriptionTopicDescribes a stream of resource state changes identified by trigger criteria and annotated with labels useful to filter projections from this topic.
    SubstanceSubstanceA homogeneous material with a definite composition.
    SubstanceDefinitionSubstanceDefinitionThe detailed description of a substance, typically at a level beyond what is used for prescribing.
    SubstanceNucleicAcidSubstanceNucleicAcidNucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction.
    SubstancePolymerSubstancePolymerProperties of a substance specific to it being a polymer.
    SubstanceProteinSubstanceProteinA SubstanceProtein is defined as a single unit of a linear amino acid sequence, or a combination of subunits that are either covalently linked or have a defined invariant stoichiometric relationship. This includes all synthetic, recombinant and purified SubstanceProteins of defined sequence, whether the use is therapeutic or prophylactic. This set of elements will be used to describe albumins, coagulation factors, cytokines, growth factors, peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant vaccines, and immunomodulators.
    SubstanceReferenceInformationSubstanceReferenceInformationTodo.
    SubstanceSourceMaterialSubstanceSourceMaterialSource material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex.
    SupplyDeliverySupplyDeliveryRecord of delivery of what is supplied.
    SupplyRequestSupplyRequestA record of a non-patient specific request for a medication, substance, device, certain types of biologically derived product, and nutrition product used in the healthcare setting.
    TaskTaskA task to be performed.
    TerminologyCapabilitiesTerminologyCapabilitiesA TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
    TestPlanTestPlanA plan for executing testing on an artifact or specifications
    TestReportTestReportA summary of information based on the results of executing a TestScript.
    TestScriptTestScriptA structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification.
    TransportTransportRecord of transport.
    ValueSetValueSetA ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [CodeSystem](https://hl7.org/fhir/R5/CodeSystem.html) definitions and their use in [coded elements](https://hl7.org/fhir/terminologies.html).
    VerificationResultVerificationResultDescribes validation requirements, source(s), status and dates for one or more elements.
    VisionPrescriptionVisionPrescriptionAn authorization for the provision of glasses and/or contact lenses to a patient.
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0354 version 2.10.0
    CodeDisplayDefinition
    OMD_O01
    OMN_O01
    OMS_O01
    ORD_O02
    ORN_O02
    ORS_O02
    RDO_O01
    RRO_O02
    ACK Varies Varies
    ADR_A19 A19 A19
    ADT_A01 A01, A04, A08, A13 A01, A04, A08, A13
    ADT_A02 A02 A02
    ADT_A03 A03 A03
    ADT_A05 A05, A14, A28, A31 A05, A14, A28, A31
    ADT_A06 A06, A07 A06, A07
    ADT_A09 A09, A10, A11 A09, A10, A11
    ADT_A12 A12 A12
    ADT_A15 A15 A15
    ADT_A16 A16 A16
    ADT_A17 A17 A17
    ADT_A28 A28, A31 A28, A31
    ADT_A18 A18 A18
    ADT_A20 A20 A20
    ADT_A21 A21, A22, A23, A25, A26, A27, A29, A32, A33 A21, A22, A23, A25, A26, A27, A29, A32, A33
    ADT_A24 A24 A24
    ADT_A30 A30, A34, A35, A36, A46, A47, A48, A49 A30, A34, A35, A36, A46, A47, A48, A49
    ADT_A37 A37 A37
    ADT_A38 A38 A38
    ADT_A39 A39, A40, A41, A42 A39, A40, A41, A42
    ARD_A19 A19 A19
    ADT_A43 A43 A43
    ADT_A44 A44 A44
    ADT_A45 A45 A45
    ADT_A50 A50, A51 A50, A51
    ADT_A52 A52, A53 A52, A53
    ADT_A54 A54, A55 A54, A55
    ADT_A60 A60 A60
    ADT_A61 A61, A62 A61, A62
    BAR_P01 P01 P01
    BAR_P02 P02 P02
    BAR_P05 P05 P05
    BAR_P06 P06 P06
    BAR_P10 P10 P10
    BAR_P12 P12 P12
    BRP_030 O30 O30
    MFD_P09 P09 P09
    BPS_O29 O29 O29
    BRP_O30 O30 O30
    BRT_O32 O32 O32
    BTS_O31 O31 O31
    CCF_I22 I22 I22
    CCI_I22 I22 I22
    CCM_I21 I21 I21
    CCQ_I19 I19 I19
    DSR_Q01 Q01 Q01
    DSR_P04 P04 P04
    CCR_I16 I16, |17, |18 I16, |17, |18
    DSR_Q03 Q03 Q03
    CCU_I20 I20 I20
    CQU_I19 I19 I19
    CRM_C01 C01, C02, C03, C04, C05, C06, C07, C08 C01, C02, C03, C04, C05, C06, C07, C08
    CSU_C09 C09, C10, C11, C12 C09, C10, C11, C12
    ORF_R02 R02, R04 R02, R04
    DBC_O41 O41 O41
    EDR_R07 R07 R07
    DBC_O42 O42 O42
    EQQ_Q04 Q04 Q04
    ORM_Q06 Q06 Q06
    DEL_O46 O46 O46
    ERP_R09 R09 R09
    DEO_O45 O45 O45
    ORR_Q06 Q06 Q06
    DER_O44 O44 O44
    DFT_P03 P03 P03
    DFT_P11 P11 P11
    DOC_T12 T12 T12
    DPR_O48 O48 O48
    DRC_O47 O47 O47
    DRG_O43 O43 O43
    PIN_I07 I07 I07
    EAC_U07 U07 U07
    MFD_MFA MFA MFA
    EAN_U09 U09 U09
    EAR_U08 U08 U08
    EHC_E01 E01 E01
    EHC_E02 E02 E02
    EHC_E04 E04 E04
    EHC_E10 E10 E10
    EHC_E12 E12 E12
    EHC_E13 E13 E13
    EHC_E15 E15 E15
    EHC_E20 E20 E20
    EHC_E21 E21 E21
    EHC_E24 E24 E24
    ESR_U02 U02 U02
    ESU_U01 U01 U01
    INR_U06 U06 U06
    RAS_O01 O01 O01
    INU_U05 U05 U05
    RAS_O02 O022 O022
    INV_U14 Events U14 U14
    LSU_U12 U12, U13 U12, U13
    MDM_T01 T01, T03, T05, T07, T09, T11 T01, T03, T05, T07, T09, T11
    MDM_T02 T02, T04, T06, T08, T10 T02, T04, T06, T08, T10
    MFK_M01 M01, M02, M03, M04, M05, M06, M07, M08, M09, M10, M11 M01, M02, M03, M04, M05, M06, M07, M08, M09, M10, M11
    MFN_M01 M01 M01
    RDS_O01 O01 O01
    MFN_M02 M02 M02
    MFN_M03 M03 M03
    MFN_M04 M04 M04
    MFN_M05 M05 M05
    RGV_O01 O01 O01
    MFN_M06 M06 M06
    MFN_M07 M07 M07
    MFN_M08 M08 M08
    RPI_I0I I01, I04 I01, I04
    MFN_M09 M09 M09
    MFN_M10 M10 M10
    MFN_M11 M11 M11
    MFN_M12 M12 M12
    RQC_I06 I06 I06
    MFN_M13 M13 M13
    RQI_I0I I01, I02, I03 I01, I02, I03
    MFN_M15 M15 M15
    MFN_M16 M16 M16
    MFN_M17 M17 M17
    MFN_M18 M18 M18
    RRD_O02 O02 O02
    MFQ_M01 M01, M02, M03, M04, M05, M06 M01, M02, M03, M04, M05, M06
    RRE_O02 O02 O02
    MFR_M01 M01, M02, M03, M01, M02, M03,
    RRG_O02 O02 O02
    MFR_M04 M04 M04
    MFR_M05 M05 M05
    MFR_M06 M06 M06
    MFR_M07 M07 M07
    NMD_N02 N02 N02
    NMQ_N01 N01 N01
    NMR_N01 N01 N01
    ORU_R31 R31 R31
    SRM_T12 T12 T12
    OMB_O27 O27 O27
    ORU_R32 R32 R32
    OMD_O03 O03 O03
    SRR_T12 T12 T12
    OMG_O19 O19 O19
    OMI_O23 O23 O23
    OML_O21 O21 O21
    OML_O33 O33 O33
    OML_O35 O35 O35
    OML_O39 O39 O39
    OML_O59 Laboratory Fulfillment request with REL segment Laboratory order message structure for fulfillment request with REL segment
    OMN_O07 O07 O07
    OMP_O09 O09 O09
    OMQ_O42 O42 O42
    OMQ_O57 O57 Identifier for the message structure for an OMQ message with a trigger event of General Order Message with Document Payload (O57)
    OMS_O05 O05 O05
    OPL_O37 O37 O37
    OPR_O38 O38 O38
    OPU_R25 R25 R25
    ORA_R33 R33 R33
    ORA_R41 R41 R41
    ORB_O28 O28 O28
    ORD_O04 O04 O04
    ORF_R04 R04 R04
    ORG_O20 O20 O20
    ORI_O24 O24 O24
    ORL_O22 O22 O22
    ORL_O34 O34 O34
    ORL_O36 O36 O36
    ORL_O40 O40 O40
    ORL_O41 O41 O41
    QRY_P04 P04 P04
    ORL_O42 O42 O42
    ORL_O43 O43 O43
    ORL_O44 O44 O44
    ORL_O53 O53 Identifier for the message structure for an ORL message with a trigger event of - General Laboratory Order Acknowledgment Message (Patient Optional) (O53)
    ORL_O54 O54 Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message – Multiple Order Per Specimen (Patient Optional) (O54)
    ORL_O55 O55 Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message – Multiple Order Per Container of Specimen (Patient Optional) (O55)
    ORL_O56 O56 Identifier for the message structure for an ORL message with a trigger event of Specimen Shipment Centric Laboratory Order Acknowledgment Message (Patient Optional) (O56)
    ORM_O01 O01 O01
    ORN_O08 O08 O08
    ORP_O10 O10 O10
    ORR_O02 O02 O02
    RDE_O01 O01 O01
    ORS_O06 O06 O06
    ORU_R01 R01 R01
    ORU_R30 R30 R30
    ORU_W01 W01 W01
    ORX_O43 O43 O43
    ORX_O58 O58 Identifier for the message structure for an ORX message with a trigger event of General Order Message with Document Payload Acknowledgement Message (O58)
    OSM_R26 R26 R26
    OSQ_Q06 Q06 Q06
    OSR_Q06 Q06 Q06
    OSU_O41 O41 O41
    OSU_O51 O51 Identifier for the message structure for an OSU message with a trigger event of Order Status Update (O51)
    OSU_O52 O52 Identifier for the message structure for an OSU message with a trigger event of Order Status Update Acknowledgement (O52)
    OUL_R21 R21 R21
    OUL_R22 R22 R22
    OUL_R23 R23 R23
    OUL_R24 R24 R24
    PEX_P07 P07, P08 P07, P08
    PGL_PC6 PC6, PC7, PC8 PC6, PC7, PC8
    PMU_B01 B01, B02 B01, B02
    RQQ_Q09 Q09 Q09
    RRA_O02 O02 O02
    PMU_B03 B03 B03
    PMU_B04 B04, B05, B06 B04, B05, B06
    PMU_B07 B07 B07
    PMU_B08 B08 B08
    PPG_PCG PCC, PCG, PCH, PCJ PCC, PCG, PCH, PCJ
    PPP_PCB PCB, PCD PCB, PCD
    PPR_PC1 PC1, PC2, PC3 PC1, PC2, PC3
    PPT_PCL PCL PCL
    PPV_PCA PCA PCA
    PRR_PC5 PC5 PC5
    PTR_PCF PCF PCF
    QBP_E03 E03 E03
    QBP_E22 E22 E22
    QBP_O33 O33 O33
    QBP_O34 O34 O34
    SPQ_Q08 Q08 Q08
    QBP_Q11 Q11 Q11
    RDY_K11 K11 K11
    QBP_Q13 Q13 Q13
    QBP_Q15 Q15 Q15
    QBP_Q21 Q21, Q22, Q23,Q24, Q25 Q21, Q22, Q23,Q24, Q25
    QCK_Q02 Q02 Q02
    QCN_J01 J01, J02 J01, J02
    RSP_K24 K24 K24
    QRF_W02 W02 W02
    QRY_A19 A19 A19
    QRY_PC4 PC4, PC9, PCE, PCK PC4, PC9, PCE, PCK
    TBR_R08 R08 R08
    QRY_Q01 Q01, Q26, Q27, Q28, Q29, Q30 Q01, Q26, Q27, Q28, Q29, Q30
    TBR_R09 R09 R09
    QRY_Q02 Q02 Q02
    QRY_R02 R02 R02
    QRY_T12 T12 T12
    VQQ_Q07 Q07 Q07
    QSB_Q16 Q16 Q16
    QVR_Q17 Q17 Q17
    RAR_RAR RAR RAR
    RAS_O17 O17 O17
    RCI_I05 I05 I05
    RCL_I06 I06 I06
    RDE_O11 O11, O25 O11, O25
    RDE_O49 Events O49 O49
    RDR_RDR RDR RDR
    RDS_O13 O13 O13
    RDY_K15 K15 K15
    REF_I12 I12, I13, I14, I15 I12, I13, I14, I15
    RER_RER RER RER
    RGR_RGR RGR RGR
    RGV_O15 O15 O15
    ROR_ROR ROR ROR
    RPA_I08 I08, I09. I10, I11 I08, I09. I10, I11
    RPI_I01 I01, I04 I01, I04
    RPI_I04 I04 I04
    RPL_I02 I02 I02
    RPR_I03 I03 I03
    RQA_I08 I08, I09, I10, I11 I08, I09, I10, I11
    RQC_I05 I05, I06 I05, I06
    RQI_I01 I01, I02, I03, I07 I01, I02, I03, I07
    RQP_I04 I04 I04
    RRA_O18 O18 O18
    RRD_O14 O14 O14
    RRE_O12 O12, O26 O12, O26
    RRE_O50 Events O50 O50
    RRG_O16 O16 O16
    RRI_I12 I12, I13, I14, I15 I12, I13, I14, I15
    RSP_E03 E03 E03
    RSP_E22 E22 E22
    RSP_K11 K11 K11
    RSP_K21 K21 K21
    RSP_K22 K22 K22
    RSP_K23 K23, K24 K23, K24
    RSP_K25 K25 K25
    RSP_K31 K31 K31
    RSP_K32 K32 K32
    RSP_O33 O33 O33
    RSP_O34 O34 O34
    RSP_Q11 Q11 Q11
    RTB_K13 K13 K13
    SDR_S31 S31, S36 S31, S36
    SDR_S32 S32, S37 S32, S37
    SET_S38 Specimen Container Preparation and Specimen Collection Event This message structure supports tracking of information related to preparations for specimen collection and the collection event.
    SET_S40 Specimen Collection Event unsuccessful This message structure supports tracking of information when specimen collection is not successful.
    SET_S41 Specimen Movement Event This message structure supports tracking of information related to the movements of specimens across locations, and placement in and out of storage.
    SET_S45 Specimen Identification Events This message structure supports tracking of information to identify or de-identify specimens or at time of final disposal.
    SET_S50 Specimen Procedure Step successful This message structure supports tracking of information related to processing of one or more specimen that may result in derived (child) specimen or not.
    SET_S52 Specimen Procedure Step unsuccessful This message structure supports tracking of information when the processing of a specimen was unsuccessful.
    SIU_S12 S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S26 S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S26
    SLR_S28 S28, S29, S30, S34, S35 S28, S29, S30, S34, S35
    SQM_S25 S25 S25
    SQR_S25 S25 S25
    SRM_S01 S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11 S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11
    SRR_S01 S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11 S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11
    QBP_Z73 Z73 Z73
    SSR_U04 U04 U04
    RSP_Z82 Z82 Z82
    SSU_U03 U03 U03
    RSP_Z86 Z86 Z86
    STC_S33 S33 S33
    RSP_Z88 Z88 Z88
    SUR_P09 P09 P09
    RSP_Z90 Z90 Z90
    TCU_U10 U10, U11 U10, U11
    RTB_Knn Knn Knn
    UDM_Q05 Q05 Q05
    RTB_Z74 Z74 Z74
    VXQ_V01 V01 V01
    QBP_Qnn Qnn Qnn
    VXR_V03 V03 V03
    VXU_V04 V04 V04
    VXX_V02 V02 V02

 

Expansion

This value set expansion contains 474 concepts.

CodeSystemDisplayDefinition
  Accounthttp://hl7.org/fhir/fhir-typesAccount

A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc.

  ActivityDefinitionhttp://hl7.org/fhir/fhir-typesActivityDefinition

This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.

  ActorDefinitionhttp://hl7.org/fhir/fhir-typesActorDefinition

The ActorDefinition resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays.

  AdministrableProductDefinitionhttp://hl7.org/fhir/fhir-typesAdministrableProductDefinition

A medicinal product in the final form which is suitable for administering to a patient (after any mixing of multiple components, dissolution etc. has been performed).

  AdverseEventhttp://hl7.org/fhir/fhir-typesAdverseEvent

An event (i.e. any change to current patient status) that may be related to unintended effects on a patient or research participant. The unintended effects may require additional monitoring, treatment, hospitalization, or may result in death. The AdverseEvent resource also extends to potential or avoided events that could have had such effects. There are two major domains where the AdverseEvent resource is expected to be used. One is in clinical care reported adverse events and the other is in reporting adverse events in clinical research trial management. Adverse events can be reported by healthcare providers, patients, caregivers or by medical products manufacturers. Given the differences between these two concepts, we recommend consulting the domain specific implementation guides when implementing the AdverseEvent Resource. The implementation guides include specific extensions, value sets and constraints.

  AllergyIntolerancehttp://hl7.org/fhir/fhir-typesAllergyIntolerance

Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance.

  Appointmenthttp://hl7.org/fhir/fhir-typesAppointment

A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).

  AppointmentResponsehttp://hl7.org/fhir/fhir-typesAppointmentResponse

A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection.

  ArtifactAssessmenthttp://hl7.org/fhir/fhir-typesArtifactAssessment

This Resource provides one or more comments, classifiers or ratings about a Resource and supports attribution and rights management metadata for the added content.

  AuditEventhttp://hl7.org/fhir/fhir-typesAuditEvent

A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis.

  Basichttp://hl7.org/fhir/fhir-typesBasic

Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.

  Binaryhttp://hl7.org/fhir/fhir-typesBinary

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.

  BiologicallyDerivedProducthttp://hl7.org/fhir/fhir-typesBiologicallyDerivedProduct

A biological material originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.

  BiologicallyDerivedProductDispensehttp://hl7.org/fhir/fhir-typesBiologicallyDerivedProductDispense

A record of dispensation of a biologically derived product.

  BodyStructurehttp://hl7.org/fhir/fhir-typesBodyStructure

Record details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.

  Bundlehttp://hl7.org/fhir/fhir-typesBundle

A container for a collection of resources.

  CapabilityStatementhttp://hl7.org/fhir/fhir-typesCapabilityStatement

A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server or Client for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.

  CarePlanhttp://hl7.org/fhir/fhir-typesCarePlan

Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.

  CareTeamhttp://hl7.org/fhir/fhir-typesCareTeam

The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care.

  ChargeItemhttp://hl7.org/fhir/fhir-typesChargeItem

The resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation.

  ChargeItemDefinitionhttp://hl7.org/fhir/fhir-typesChargeItemDefinition

The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system.

  Citationhttp://hl7.org/fhir/fhir-typesCitation

The Citation Resource enables reference to any knowledge artifact for purposes of identification and attribution. The Citation Resource supports existing reference structures and developing publication practices such as versioning, expressing complex contributorship roles, and referencing computable resources.

  Claimhttp://hl7.org/fhir/fhir-typesClaim

A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement.

  ClaimResponsehttp://hl7.org/fhir/fhir-typesClaimResponse

This resource provides the adjudication details from the processing of a Claim resource.

  ClinicalImpressionhttp://hl7.org/fhir/fhir-typesClinicalImpression

A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with the recording of assessment tools such as Apgar score.

  ClinicalUseDefinitionhttp://hl7.org/fhir/fhir-typesClinicalUseDefinition

A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.

  CodeSystemhttp://hl7.org/fhir/fhir-typesCodeSystem

The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content.

  Communicationhttp://hl7.org/fhir/fhir-typesCommunication

A clinical or business level record of information being transmitted or shared; e.g. an alert that was sent to a responsible provider, a public health agency communication to a provider/reporter in response to a case report for a reportable condition.

  CommunicationRequesthttp://hl7.org/fhir/fhir-typesCommunicationRequest

A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition.

  CompartmentDefinitionhttp://hl7.org/fhir/fhir-typesCompartmentDefinition

A compartment definition that defines how resources are accessed on a server.

  Compositionhttp://hl7.org/fhir/fhir-typesComposition

A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.).

  ConceptMaphttp://hl7.org/fhir/fhir-typesConceptMap

A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models.

  Conditionhttp://hl7.org/fhir/fhir-typesCondition

A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.

  ConditionDefinitionhttp://hl7.org/fhir/fhir-typesConditionDefinition

A definition of a condition and information relevant to managing it.

  Consenthttp://hl7.org/fhir/fhir-typesConsent

A record of a healthcare consumer’s choices or choices made on their behalf by a third party, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

  Contracthttp://hl7.org/fhir/fhir-typesContract

Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement.

  Coveragehttp://hl7.org/fhir/fhir-typesCoverage

Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.

  CoverageEligibilityRequesthttp://hl7.org/fhir/fhir-typesCoverageEligibilityRequest

The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy.

  CoverageEligibilityResponsehttp://hl7.org/fhir/fhir-typesCoverageEligibilityResponse

This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource.

  DetectedIssuehttp://hl7.org/fhir/fhir-typesDetectedIssue

Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, gaps in care, etc.

  Devicehttp://hl7.org/fhir/fhir-typesDevice

This resource describes the properties (regulated, has real time clock, etc.), adminstrative (manufacturer name, model number, serial number, firmware, etc.), and type (knee replacement, blood pressure cuff, MRI, etc.) of a physical unit (these values do not change much within a given module, for example the serail number, manufacturer name, and model number). An actual unit may consist of several modules in a distinct hierarchy and these are represented by multiple Device resources and bound through the 'parent' element.

  DeviceAssociationhttp://hl7.org/fhir/fhir-typesDeviceAssociation

A record of association of a device.

  DeviceDefinitionhttp://hl7.org/fhir/fhir-typesDeviceDefinition

This is a specialized resource that defines the characteristics and capabilities of a device.

  DeviceDispensehttp://hl7.org/fhir/fhir-typesDeviceDispense

Indicates that a device is to be or has been dispensed for a named person/patient. This includes a description of the product (supply) provided and the instructions for using the device.

  DeviceMetrichttp://hl7.org/fhir/fhir-typesDeviceMetric

Describes a measurement, calculation or setting capability of a device. The DeviceMetric resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable.

  DeviceRequesthttp://hl7.org/fhir/fhir-typesDeviceRequest

Represents a request a device to be provided to a specific patient. The device may be an implantable device to be subsequently implanted, or an external assistive device, such as a walker, to be delivered and subsequently be used.

  DeviceUsagehttp://hl7.org/fhir/fhir-typesDeviceUsage

A record of a device being used by a patient where the record is the result of a report from the patient or a clinician.

  DiagnosticReporthttp://hl7.org/fhir/fhir-typesDiagnosticReport

The findings and interpretation of diagnostic tests performed on patients, groups of patients, products, substances, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. The report also includes non-clinical context such as batch analysis and stability reporting of products and substances.

  DocumentReferencehttp://hl7.org/fhir/fhir-typesDocumentReference

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.

  Encounterhttp://hl7.org/fhir/fhir-typesEncounter

An interaction between healthcare provider(s), and/or patient(s) for the purpose of providing healthcare service(s) or assessing the health status of patient(s).

  EncounterHistoryhttp://hl7.org/fhir/fhir-typesEncounterHistory

A record of significant events/milestones key data throughout the history of an Encounter

  Endpointhttp://hl7.org/fhir/fhir-typesEndpoint

The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b, a REST endpoint for another FHIR server, or a s/Mime email address. This may include any security context information.

  EnrollmentRequesthttp://hl7.org/fhir/fhir-typesEnrollmentRequest

This resource provides the insurance enrollment details to the insurer regarding a specified coverage.

  EnrollmentResponsehttp://hl7.org/fhir/fhir-typesEnrollmentResponse

This resource provides enrollment and plan details from the processing of an EnrollmentRequest resource.

  EpisodeOfCarehttp://hl7.org/fhir/fhir-typesEpisodeOfCare

An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time.

  EventDefinitionhttp://hl7.org/fhir/fhir-typesEventDefinition

The EventDefinition resource provides a reusable description of when a particular event can occur.

  Evidencehttp://hl7.org/fhir/fhir-typesEvidence

The Evidence Resource provides a machine-interpretable expression of an evidence concept including the evidence variables (e.g., population, exposures/interventions, comparators, outcomes, measured variables, confounding variables), the statistics, and the certainty of this evidence.

  EvidenceReporthttp://hl7.org/fhir/fhir-typesEvidenceReport

The EvidenceReport Resource is a specialized container for a collection of resources and codeable concepts, adapted to support compositions of Evidence, EvidenceVariable, and Citation resources and related concepts.

  EvidenceVariablehttp://hl7.org/fhir/fhir-typesEvidenceVariable

The EvidenceVariable resource describes an element that knowledge (Evidence) is about.

  ExampleScenariohttp://hl7.org/fhir/fhir-typesExampleScenario

A walkthrough of a workflow showing the interaction between systems and the instances shared, possibly including the evolution of instances over time.

  ExplanationOfBenefithttp://hl7.org/fhir/fhir-typesExplanationOfBenefit

This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided.

  FamilyMemberHistoryhttp://hl7.org/fhir/fhir-typesFamilyMemberHistory

Significant health conditions for a person related to the patient relevant in the context of care for the patient.

  Flaghttp://hl7.org/fhir/fhir-typesFlag

Prospective warnings of potential issues when providing care to the patient.

  FormularyItemhttp://hl7.org/fhir/fhir-typesFormularyItem

This resource describes a product or service that is available through a program and includes the conditions and constraints of availability. All of the information in this resource is specific to the inclusion of the item in the formulary and is not inherent to the item itself.

  GenomicStudyhttp://hl7.org/fhir/fhir-typesGenomicStudy

A set of analyses performed to analyze and generate genomic data.

  Goalhttp://hl7.org/fhir/fhir-typesGoal

Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.

  GraphDefinitionhttp://hl7.org/fhir/fhir-typesGraphDefinition

A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set.

  Grouphttp://hl7.org/fhir/fhir-typesGroup

Represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization.

  GuidanceResponsehttp://hl7.org/fhir/fhir-typesGuidanceResponse

A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken.

  HealthcareServicehttp://hl7.org/fhir/fhir-typesHealthcareService

The details of a healthcare service available at a location or in a catalog. In the case where there is a hierarchy of services (for example, Lab -> Pathology -> Wound Cultures), this can be represented using a set of linked HealthcareServices.

  ImagingSelectionhttp://hl7.org/fhir/fhir-typesImagingSelection

A selection of DICOM SOP instances and/or frames within a single Study and Series. This might include additional specifics such as an image region, an Observation UID or a Segmentation Number, allowing linkage to an Observation Resource or transferring this information along with the ImagingStudy Resource.

  ImagingStudyhttp://hl7.org/fhir/fhir-typesImagingStudy

Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities.

  Immunizationhttp://hl7.org/fhir/fhir-typesImmunization

Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.

  ImmunizationEvaluationhttp://hl7.org/fhir/fhir-typesImmunizationEvaluation

Describes a comparison of an immunization event against published recommendations to determine if the administration is "valid" in relation to those recommendations.

  ImmunizationRecommendationhttp://hl7.org/fhir/fhir-typesImmunizationRecommendation

A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification.

  ImplementationGuidehttp://hl7.org/fhir/fhir-typesImplementationGuide

A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts.

  Ingredienthttp://hl7.org/fhir/fhir-typesIngredient

An ingredient of a manufactured item or pharmaceutical product.

  InsurancePlanhttp://hl7.org/fhir/fhir-typesInsurancePlan

Details of a Health Insurance product/plan provided by an organization.

  InventoryItemhttp://hl7.org/fhir/fhir-typesInventoryItem

functional description of an inventory item used in inventory and supply-related workflows.

  InventoryReporthttp://hl7.org/fhir/fhir-typesInventoryReport

A report of inventory or stock items.

  Invoicehttp://hl7.org/fhir/fhir-typesInvoice

Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.

  Libraryhttp://hl7.org/fhir/fhir-typesLibrary

The Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose existing knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets.

  Linkagehttp://hl7.org/fhir/fhir-typesLinkage

Identifies two or more records (resource instances) that refer to the same real-world "occurrence".

  Listhttp://hl7.org/fhir/fhir-typesList

A List is a curated collection of resources, for things such as problem lists, allergy lists, facility list, organization list, etc.

  Locationhttp://hl7.org/fhir/fhir-typesLocation

Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.

  ManufacturedItemDefinitionhttp://hl7.org/fhir/fhir-typesManufacturedItemDefinition

The definition and characteristics of a medicinal manufactured item, such as a tablet or capsule, as contained in a packaged medicinal product.

  Measurehttp://hl7.org/fhir/fhir-typesMeasure

The Measure resource provides the definition of a quality measure.

  MeasureReporthttp://hl7.org/fhir/fhir-typesMeasureReport

The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation.

  Medicationhttp://hl7.org/fhir/fhir-typesMedication

This resource is primarily used for the identification and definition of a medication, including ingredients, for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.

  MedicationAdministrationhttp://hl7.org/fhir/fhir-typesMedicationAdministration

Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. This event can also be used to record waste using a status of not-done and the appropriate statusReason.

  MedicationDispensehttp://hl7.org/fhir/fhir-typesMedicationDispense

Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.

  MedicationKnowledgehttp://hl7.org/fhir/fhir-typesMedicationKnowledge

Information about a medication that is used to support knowledge.

  MedicationRequesthttp://hl7.org/fhir/fhir-typesMedicationRequest

An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.

  MedicationStatementhttp://hl7.org/fhir/fhir-typesMedicationStatement

A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains.

The primary difference between a medicationstatement and a medicationadministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medicationstatement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the Medication Statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information.

  MedicinalProductDefinitionhttp://hl7.org/fhir/fhir-typesMedicinalProductDefinition

Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use, drug catalogs, to support prescribing, adverse events management etc.).

  MessageDefinitionhttp://hl7.org/fhir/fhir-typesMessageDefinition

Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted.

  MessageHeaderhttp://hl7.org/fhir/fhir-typesMessageHeader

The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.

  MolecularSequencehttp://hl7.org/fhir/fhir-typesMolecularSequence

Representation of a molecular sequence.

  NamingSystemhttp://hl7.org/fhir/fhir-typesNamingSystem

A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types.

  NutritionIntakehttp://hl7.org/fhir/fhir-typesNutritionIntake

A record of food or fluid that is being consumed by a patient. A NutritionIntake may indicate that the patient may be consuming the food or fluid now or has consumed the food or fluid in the past. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay or through an app that tracks food or fluids consumed. The consumption information may come from sources such as the patient's memory, from a nutrition label, or from a clinician documenting observed intake.

  NutritionOrderhttp://hl7.org/fhir/fhir-typesNutritionOrder

A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident.

  NutritionProducthttp://hl7.org/fhir/fhir-typesNutritionProduct

A food or supplement that is consumed by patients.

  Observationhttp://hl7.org/fhir/fhir-typesObservation

Measurements and simple assertions made about a patient, device or other subject.

  ObservationDefinitionhttp://hl7.org/fhir/fhir-typesObservationDefinition

Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service.

  OperationDefinitionhttp://hl7.org/fhir/fhir-typesOperationDefinition

A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).

  OperationOutcomehttp://hl7.org/fhir/fhir-typesOperationOutcome

A collection of error, warning, or information messages that result from a system action.

  Organizationhttp://hl7.org/fhir/fhir-typesOrganization

A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.

  OrganizationAffiliationhttp://hl7.org/fhir/fhir-typesOrganizationAffiliation

Defines an affiliation/assotiation/relationship between 2 distinct organizations, that is not a part-of relationship/sub-division relationship.

  PackagedProductDefinitionhttp://hl7.org/fhir/fhir-typesPackagedProductDefinition

A medically related item or items, in a container or package.

  Parametershttp://hl7.org/fhir/fhir-typesParameters

This resource is used to pass information into and back from an operation (whether invoked directly from REST or within a messaging environment). It is not persisted or allowed to be referenced by other resources except as described in the definition of the Parameters resource.

  Patienthttp://hl7.org/fhir/fhir-typesPatient

Demographics and other administrative information about an individual or animal receiving care or other health-related services.

  PaymentNoticehttp://hl7.org/fhir/fhir-typesPaymentNotice

This resource provides the status of the payment for goods and services rendered, and the request and response resource references.

  PaymentReconciliationhttp://hl7.org/fhir/fhir-typesPaymentReconciliation

This resource provides the details including amount of a payment and allocates the payment items being paid.

  Permissionhttp://hl7.org/fhir/fhir-typesPermission

Permission resource holds access rules for a given data and context.

  Personhttp://hl7.org/fhir/fhir-typesPerson

Demographics and administrative information about a person independent of a specific health-related context.

  PlanDefinitionhttp://hl7.org/fhir/fhir-typesPlanDefinition

This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical and non-clinical artifacts such as clinical decision support rules, order sets, protocols, and drug quality specifications.

  Practitionerhttp://hl7.org/fhir/fhir-typesPractitioner

A person who is directly or indirectly involved in the provisioning of healthcare or related services.

  PractitionerRolehttp://hl7.org/fhir/fhir-typesPractitionerRole

A specific set of Roles/Locations/specialties/services that a practitioner may perform, or has performed at an organization during a period of time.

  Procedurehttp://hl7.org/fhir/fhir-typesProcedure

An action that is or was performed on or for a patient, practitioner, device, organization, or location. For example, this can be a physical intervention on a patient like an operation, or less invasive like long term services, counseling, or hypnotherapy. This can be a quality or safety inspection for a location, organization, or device. This can be an accreditation procedure on a practitioner for licensing.

  Provenancehttp://hl7.org/fhir/fhir-typesProvenance

Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies.

  Questionnairehttp://hl7.org/fhir/fhir-typesQuestionnaire

A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.

  QuestionnaireResponsehttp://hl7.org/fhir/fhir-typesQuestionnaireResponse

A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to.

  RegulatedAuthorizationhttp://hl7.org/fhir/fhir-typesRegulatedAuthorization

Regulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity that is cited in a guidance, regulation, rule or legislative act. An example is Market Authorization relating to a Medicinal Product.

  RelatedPersonhttp://hl7.org/fhir/fhir-typesRelatedPerson

Information about a person that is involved in a patient's health or the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.

  RequestOrchestrationhttp://hl7.org/fhir/fhir-typesRequestOrchestration

A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one".

  Requirementshttp://hl7.org/fhir/fhir-typesRequirements

The Requirements resource is used to describe an actor - a human or an application that plays a role in data exchange, and that may have obligations associated with the role the actor plays.

  ResearchStudyhttp://hl7.org/fhir/fhir-typesResearchStudy

A scientific study of nature that sometimes includes processes involved in health and disease. For example, clinical trials are research studies that involve people. These studies may be related to new ways to screen, prevent, diagnose, and treat disease. They may also study certain outcomes and certain groups of people by looking at data collected in the past or future.

  ResearchSubjecthttp://hl7.org/fhir/fhir-typesResearchSubject

A ResearchSubject is a participant or object which is the recipient of investigative activities in a research study.

  RiskAssessmenthttp://hl7.org/fhir/fhir-typesRiskAssessment

An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome.

  Schedulehttp://hl7.org/fhir/fhir-typesSchedule

A container for slots of time that may be available for booking appointments.

  SearchParameterhttp://hl7.org/fhir/fhir-typesSearchParameter

A search parameter that defines a named search item that can be used to search/filter on a resource.

  ServiceRequesthttp://hl7.org/fhir/fhir-typesServiceRequest

A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.

  Slothttp://hl7.org/fhir/fhir-typesSlot

A slot of time on a schedule that may be available for booking appointments.

  Specimenhttp://hl7.org/fhir/fhir-typesSpecimen

A sample to be used for analysis.

  SpecimenDefinitionhttp://hl7.org/fhir/fhir-typesSpecimenDefinition

A kind of specimen with associated set of requirements.

  StructureDefinitionhttp://hl7.org/fhir/fhir-typesStructureDefinition

A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types.

  StructureMaphttp://hl7.org/fhir/fhir-typesStructureMap

A Map of relationships between 2 structures that can be used to transform data.

  Subscriptionhttp://hl7.org/fhir/fhir-typesSubscription

The subscription resource describes a particular client's request to be notified about a SubscriptionTopic.

  SubscriptionStatushttp://hl7.org/fhir/fhir-typesSubscriptionStatus

The SubscriptionStatus resource describes the state of a Subscription during notifications. It is not persisted.

  SubscriptionTopichttp://hl7.org/fhir/fhir-typesSubscriptionTopic

Describes a stream of resource state changes identified by trigger criteria and annotated with labels useful to filter projections from this topic.

  Substancehttp://hl7.org/fhir/fhir-typesSubstance

A homogeneous material with a definite composition.

  SubstanceDefinitionhttp://hl7.org/fhir/fhir-typesSubstanceDefinition

The detailed description of a substance, typically at a level beyond what is used for prescribing.

  SubstanceNucleicAcidhttp://hl7.org/fhir/fhir-typesSubstanceNucleicAcid

Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction.

  SubstancePolymerhttp://hl7.org/fhir/fhir-typesSubstancePolymer

Properties of a substance specific to it being a polymer.

  SubstanceProteinhttp://hl7.org/fhir/fhir-typesSubstanceProtein

A SubstanceProtein is defined as a single unit of a linear amino acid sequence, or a combination of subunits that are either covalently linked or have a defined invariant stoichiometric relationship. This includes all synthetic, recombinant and purified SubstanceProteins of defined sequence, whether the use is therapeutic or prophylactic. This set of elements will be used to describe albumins, coagulation factors, cytokines, growth factors, peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant vaccines, and immunomodulators.

  SubstanceReferenceInformationhttp://hl7.org/fhir/fhir-typesSubstanceReferenceInformation

Todo.

  SubstanceSourceMaterialhttp://hl7.org/fhir/fhir-typesSubstanceSourceMaterial

Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex.

  SupplyDeliveryhttp://hl7.org/fhir/fhir-typesSupplyDelivery

Record of delivery of what is supplied.

  SupplyRequesthttp://hl7.org/fhir/fhir-typesSupplyRequest

A record of a non-patient specific request for a medication, substance, device, certain types of biologically derived product, and nutrition product used in the healthcare setting.

  Taskhttp://hl7.org/fhir/fhir-typesTask

A task to be performed.

  TerminologyCapabilitieshttp://hl7.org/fhir/fhir-typesTerminologyCapabilities

A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation.

  TestPlanhttp://hl7.org/fhir/fhir-typesTestPlan

A plan for executing testing on an artifact or specifications

  TestReporthttp://hl7.org/fhir/fhir-typesTestReport

A summary of information based on the results of executing a TestScript.

  TestScripthttp://hl7.org/fhir/fhir-typesTestScript

A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification.

  Transporthttp://hl7.org/fhir/fhir-typesTransport

Record of transport.

  ValueSethttp://hl7.org/fhir/fhir-typesValueSet

A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between CodeSystem definitions and their use in coded elements.

  VerificationResulthttp://hl7.org/fhir/fhir-typesVerificationResult

Describes validation requirements, source(s), status and dates for one or more elements.

  VisionPrescriptionhttp://hl7.org/fhir/fhir-typesVisionPrescription

An authorization for the provision of glasses and/or contact lenses to a patient.

  OMD_O01http://terminology.hl7.org/CodeSystem/v2-0354
  OMN_O01http://terminology.hl7.org/CodeSystem/v2-0354
  OMS_O01http://terminology.hl7.org/CodeSystem/v2-0354
  ORD_O02http://terminology.hl7.org/CodeSystem/v2-0354
  ORN_O02http://terminology.hl7.org/CodeSystem/v2-0354
  ORS_O02http://terminology.hl7.org/CodeSystem/v2-0354
  RDO_O01http://terminology.hl7.org/CodeSystem/v2-0354
  RRO_O02http://terminology.hl7.org/CodeSystem/v2-0354
  ACKhttp://terminology.hl7.org/CodeSystem/v2-0354VariesVaries
  ADR_A19http://terminology.hl7.org/CodeSystem/v2-0354A19A19
  ADT_A01http://terminology.hl7.org/CodeSystem/v2-0354A01, A04, A08, A13A01, A04, A08, A13
  ADT_A02http://terminology.hl7.org/CodeSystem/v2-0354A02A02
  ADT_A03http://terminology.hl7.org/CodeSystem/v2-0354A03A03
  ADT_A05http://terminology.hl7.org/CodeSystem/v2-0354A05, A14, A28, A31A05, A14, A28, A31
  ADT_A06http://terminology.hl7.org/CodeSystem/v2-0354A06, A07A06, A07
  ADT_A09http://terminology.hl7.org/CodeSystem/v2-0354A09, A10, A11A09, A10, A11
  ADT_A12http://terminology.hl7.org/CodeSystem/v2-0354A12A12
  ADT_A15http://terminology.hl7.org/CodeSystem/v2-0354A15A15
  ADT_A16http://terminology.hl7.org/CodeSystem/v2-0354A16A16
  ADT_A17http://terminology.hl7.org/CodeSystem/v2-0354A17A17
  ADT_A28http://terminology.hl7.org/CodeSystem/v2-0354A28, A31A28, A31
  ADT_A18http://terminology.hl7.org/CodeSystem/v2-0354A18A18
  ADT_A20http://terminology.hl7.org/CodeSystem/v2-0354A20A20
  ADT_A21http://terminology.hl7.org/CodeSystem/v2-0354A21, A22, A23, A25, A26, A27, A29, A32, A33A21, A22, A23, A25, A26, A27, A29, A32, A33
  ADT_A24http://terminology.hl7.org/CodeSystem/v2-0354A24A24
  ADT_A30http://terminology.hl7.org/CodeSystem/v2-0354A30, A34, A35, A36, A46, A47, A48, A49A30, A34, A35, A36, A46, A47, A48, A49
  ADT_A37http://terminology.hl7.org/CodeSystem/v2-0354A37A37
  ADT_A38http://terminology.hl7.org/CodeSystem/v2-0354A38A38
  ADT_A39http://terminology.hl7.org/CodeSystem/v2-0354A39, A40, A41, A42A39, A40, A41, A42
  ARD_A19http://terminology.hl7.org/CodeSystem/v2-0354A19A19
  ADT_A43http://terminology.hl7.org/CodeSystem/v2-0354A43A43
  ADT_A44http://terminology.hl7.org/CodeSystem/v2-0354A44A44
  ADT_A45http://terminology.hl7.org/CodeSystem/v2-0354A45A45
  ADT_A50http://terminology.hl7.org/CodeSystem/v2-0354A50, A51A50, A51
  ADT_A52http://terminology.hl7.org/CodeSystem/v2-0354A52, A53A52, A53
  ADT_A54http://terminology.hl7.org/CodeSystem/v2-0354A54, A55A54, A55
  ADT_A60http://terminology.hl7.org/CodeSystem/v2-0354A60A60
  ADT_A61http://terminology.hl7.org/CodeSystem/v2-0354A61, A62A61, A62
  BAR_P01http://terminology.hl7.org/CodeSystem/v2-0354P01P01
  BAR_P02http://terminology.hl7.org/CodeSystem/v2-0354P02P02
  BAR_P05http://terminology.hl7.org/CodeSystem/v2-0354P05P05
  BAR_P06http://terminology.hl7.org/CodeSystem/v2-0354P06P06
  BAR_P10http://terminology.hl7.org/CodeSystem/v2-0354P10P10
  BAR_P12http://terminology.hl7.org/CodeSystem/v2-0354P12P12
  BRP_030http://terminology.hl7.org/CodeSystem/v2-0354O30O30
  MFD_P09http://terminology.hl7.org/CodeSystem/v2-0354P09P09
  BPS_O29http://terminology.hl7.org/CodeSystem/v2-0354O29O29
  BRP_O30http://terminology.hl7.org/CodeSystem/v2-0354O30O30
  BRT_O32http://terminology.hl7.org/CodeSystem/v2-0354O32O32
  BTS_O31http://terminology.hl7.org/CodeSystem/v2-0354O31O31
  CCF_I22http://terminology.hl7.org/CodeSystem/v2-0354I22I22
  CCI_I22http://terminology.hl7.org/CodeSystem/v2-0354I22I22
  CCM_I21http://terminology.hl7.org/CodeSystem/v2-0354I21I21
  CCQ_I19http://terminology.hl7.org/CodeSystem/v2-0354I19I19
  DSR_Q01http://terminology.hl7.org/CodeSystem/v2-0354Q01Q01
  DSR_P04http://terminology.hl7.org/CodeSystem/v2-0354P04P04
  CCR_I16http://terminology.hl7.org/CodeSystem/v2-0354I16, |17, |18I16, |17, |18
  DSR_Q03http://terminology.hl7.org/CodeSystem/v2-0354Q03Q03
  CCU_I20http://terminology.hl7.org/CodeSystem/v2-0354I20I20
  CQU_I19http://terminology.hl7.org/CodeSystem/v2-0354I19I19
  CRM_C01http://terminology.hl7.org/CodeSystem/v2-0354C01, C02, C03, C04, C05, C06, C07, C08C01, C02, C03, C04, C05, C06, C07, C08
  CSU_C09http://terminology.hl7.org/CodeSystem/v2-0354C09, C10, C11, C12C09, C10, C11, C12
  ORF_R02http://terminology.hl7.org/CodeSystem/v2-0354R02, R04R02, R04
  DBC_O41http://terminology.hl7.org/CodeSystem/v2-0354O41O41
  EDR_R07http://terminology.hl7.org/CodeSystem/v2-0354R07R07
  DBC_O42http://terminology.hl7.org/CodeSystem/v2-0354O42O42
  EQQ_Q04http://terminology.hl7.org/CodeSystem/v2-0354Q04Q04
  ORM_Q06http://terminology.hl7.org/CodeSystem/v2-0354Q06Q06
  DEL_O46http://terminology.hl7.org/CodeSystem/v2-0354O46O46
  ERP_R09http://terminology.hl7.org/CodeSystem/v2-0354R09R09
  DEO_O45http://terminology.hl7.org/CodeSystem/v2-0354O45O45
  ORR_Q06http://terminology.hl7.org/CodeSystem/v2-0354Q06Q06
  DER_O44http://terminology.hl7.org/CodeSystem/v2-0354O44O44
  DFT_P03http://terminology.hl7.org/CodeSystem/v2-0354P03P03
  DFT_P11http://terminology.hl7.org/CodeSystem/v2-0354P11P11
  DOC_T12http://terminology.hl7.org/CodeSystem/v2-0354T12T12
  DPR_O48http://terminology.hl7.org/CodeSystem/v2-0354O48O48
  DRC_O47http://terminology.hl7.org/CodeSystem/v2-0354O47O47
  DRG_O43http://terminology.hl7.org/CodeSystem/v2-0354O43O43
  PIN_I07http://terminology.hl7.org/CodeSystem/v2-0354I07I07
  EAC_U07http://terminology.hl7.org/CodeSystem/v2-0354U07U07
  MFD_MFAhttp://terminology.hl7.org/CodeSystem/v2-0354MFAMFA
  EAN_U09http://terminology.hl7.org/CodeSystem/v2-0354U09U09
  EAR_U08http://terminology.hl7.org/CodeSystem/v2-0354U08U08
  EHC_E01http://terminology.hl7.org/CodeSystem/v2-0354E01E01
  EHC_E02http://terminology.hl7.org/CodeSystem/v2-0354E02E02
  EHC_E04http://terminology.hl7.org/CodeSystem/v2-0354E04E04
  EHC_E10http://terminology.hl7.org/CodeSystem/v2-0354E10E10
  EHC_E12http://terminology.hl7.org/CodeSystem/v2-0354E12E12
  EHC_E13http://terminology.hl7.org/CodeSystem/v2-0354E13E13
  EHC_E15http://terminology.hl7.org/CodeSystem/v2-0354E15E15
  EHC_E20http://terminology.hl7.org/CodeSystem/v2-0354E20E20
  EHC_E21http://terminology.hl7.org/CodeSystem/v2-0354E21E21
  EHC_E24http://terminology.hl7.org/CodeSystem/v2-0354E24E24
  ESR_U02http://terminology.hl7.org/CodeSystem/v2-0354U02U02
  ESU_U01http://terminology.hl7.org/CodeSystem/v2-0354U01U01
  INR_U06http://terminology.hl7.org/CodeSystem/v2-0354U06U06
  RAS_O01http://terminology.hl7.org/CodeSystem/v2-0354O01O01
  INU_U05http://terminology.hl7.org/CodeSystem/v2-0354U05U05
  RAS_O02http://terminology.hl7.org/CodeSystem/v2-0354O022O022
  INV_U14http://terminology.hl7.org/CodeSystem/v2-0354Events U14U14
  LSU_U12http://terminology.hl7.org/CodeSystem/v2-0354U12, U13U12, U13
  MDM_T01http://terminology.hl7.org/CodeSystem/v2-0354T01, T03, T05, T07, T09, T11T01, T03, T05, T07, T09, T11
  MDM_T02http://terminology.hl7.org/CodeSystem/v2-0354T02, T04, T06, T08, T10T02, T04, T06, T08, T10
  MFK_M01http://terminology.hl7.org/CodeSystem/v2-0354M01, M02, M03, M04, M05, M06, M07, M08, M09, M10, M11M01, M02, M03, M04, M05, M06, M07, M08, M09, M10, M11
  MFN_M01http://terminology.hl7.org/CodeSystem/v2-0354M01M01
  RDS_O01http://terminology.hl7.org/CodeSystem/v2-0354O01O01
  MFN_M02http://terminology.hl7.org/CodeSystem/v2-0354M02M02
  MFN_M03http://terminology.hl7.org/CodeSystem/v2-0354M03M03
  MFN_M04http://terminology.hl7.org/CodeSystem/v2-0354M04M04
  MFN_M05http://terminology.hl7.org/CodeSystem/v2-0354M05M05
  RGV_O01http://terminology.hl7.org/CodeSystem/v2-0354O01O01
  MFN_M06http://terminology.hl7.org/CodeSystem/v2-0354M06M06
  MFN_M07http://terminology.hl7.org/CodeSystem/v2-0354M07M07
  MFN_M08http://terminology.hl7.org/CodeSystem/v2-0354M08M08
  RPI_I0Ihttp://terminology.hl7.org/CodeSystem/v2-0354I01, I04I01, I04
  MFN_M09http://terminology.hl7.org/CodeSystem/v2-0354M09M09
  MFN_M10http://terminology.hl7.org/CodeSystem/v2-0354M10M10
  MFN_M11http://terminology.hl7.org/CodeSystem/v2-0354M11M11
  MFN_M12http://terminology.hl7.org/CodeSystem/v2-0354M12M12
  RQC_I06http://terminology.hl7.org/CodeSystem/v2-0354I06I06
  MFN_M13http://terminology.hl7.org/CodeSystem/v2-0354M13M13
  RQI_I0Ihttp://terminology.hl7.org/CodeSystem/v2-0354I01, I02, I03I01, I02, I03
  MFN_M15http://terminology.hl7.org/CodeSystem/v2-0354M15M15
  MFN_M16http://terminology.hl7.org/CodeSystem/v2-0354M16M16
  MFN_M17http://terminology.hl7.org/CodeSystem/v2-0354M17M17
  MFN_M18http://terminology.hl7.org/CodeSystem/v2-0354M18M18
  RRD_O02http://terminology.hl7.org/CodeSystem/v2-0354O02O02
  MFQ_M01http://terminology.hl7.org/CodeSystem/v2-0354M01, M02, M03, M04, M05, M06M01, M02, M03, M04, M05, M06
  RRE_O02http://terminology.hl7.org/CodeSystem/v2-0354O02O02
  MFR_M01http://terminology.hl7.org/CodeSystem/v2-0354M01, M02, M03,M01, M02, M03,
  RRG_O02http://terminology.hl7.org/CodeSystem/v2-0354O02O02
  MFR_M04http://terminology.hl7.org/CodeSystem/v2-0354M04M04
  MFR_M05http://terminology.hl7.org/CodeSystem/v2-0354M05M05
  MFR_M06http://terminology.hl7.org/CodeSystem/v2-0354M06M06
  MFR_M07http://terminology.hl7.org/CodeSystem/v2-0354M07M07
  NMD_N02http://terminology.hl7.org/CodeSystem/v2-0354N02N02
  NMQ_N01http://terminology.hl7.org/CodeSystem/v2-0354N01N01
  NMR_N01http://terminology.hl7.org/CodeSystem/v2-0354N01N01
  ORU_R31http://terminology.hl7.org/CodeSystem/v2-0354R31R31
  SRM_T12http://terminology.hl7.org/CodeSystem/v2-0354T12T12
  OMB_O27http://terminology.hl7.org/CodeSystem/v2-0354O27O27
  ORU_R32http://terminology.hl7.org/CodeSystem/v2-0354R32R32
  OMD_O03http://terminology.hl7.org/CodeSystem/v2-0354O03O03
  SRR_T12http://terminology.hl7.org/CodeSystem/v2-0354T12T12
  OMG_O19http://terminology.hl7.org/CodeSystem/v2-0354O19O19
  OMI_O23http://terminology.hl7.org/CodeSystem/v2-0354O23O23
  OML_O21http://terminology.hl7.org/CodeSystem/v2-0354O21O21
  OML_O33http://terminology.hl7.org/CodeSystem/v2-0354O33O33
  OML_O35http://terminology.hl7.org/CodeSystem/v2-0354O35O35
  OML_O39http://terminology.hl7.org/CodeSystem/v2-0354O39O39
  OML_O59http://terminology.hl7.org/CodeSystem/v2-0354Laboratory Fulfillment request with REL segmentLaboratory order message structure for fulfillment request with REL segment
  OMN_O07http://terminology.hl7.org/CodeSystem/v2-0354O07O07
  OMP_O09http://terminology.hl7.org/CodeSystem/v2-0354O09O09
  OMQ_O42http://terminology.hl7.org/CodeSystem/v2-0354O42O42
  OMQ_O57http://terminology.hl7.org/CodeSystem/v2-0354O57Identifier for the message structure for an OMQ message with a trigger event of General Order Message with Document Payload (O57)
  OMS_O05http://terminology.hl7.org/CodeSystem/v2-0354O05O05
  OPL_O37http://terminology.hl7.org/CodeSystem/v2-0354O37O37
  OPR_O38http://terminology.hl7.org/CodeSystem/v2-0354O38O38
  OPU_R25http://terminology.hl7.org/CodeSystem/v2-0354R25R25
  ORA_R33http://terminology.hl7.org/CodeSystem/v2-0354R33R33
  ORA_R41http://terminology.hl7.org/CodeSystem/v2-0354R41R41
  ORB_O28http://terminology.hl7.org/CodeSystem/v2-0354O28O28
  ORD_O04http://terminology.hl7.org/CodeSystem/v2-0354O04O04
  ORF_R04http://terminology.hl7.org/CodeSystem/v2-0354R04R04
  ORG_O20http://terminology.hl7.org/CodeSystem/v2-0354O20O20
  ORI_O24http://terminology.hl7.org/CodeSystem/v2-0354O24O24
  ORL_O22http://terminology.hl7.org/CodeSystem/v2-0354O22O22
  ORL_O34http://terminology.hl7.org/CodeSystem/v2-0354O34O34
  ORL_O36http://terminology.hl7.org/CodeSystem/v2-0354O36O36
  ORL_O40http://terminology.hl7.org/CodeSystem/v2-0354O40O40
  ORL_O41http://terminology.hl7.org/CodeSystem/v2-0354O41O41
  QRY_P04http://terminology.hl7.org/CodeSystem/v2-0354P04P04
  ORL_O42http://terminology.hl7.org/CodeSystem/v2-0354O42O42
  ORL_O43http://terminology.hl7.org/CodeSystem/v2-0354O43O43
  ORL_O44http://terminology.hl7.org/CodeSystem/v2-0354O44O44
  ORL_O53http://terminology.hl7.org/CodeSystem/v2-0354O53Identifier for the message structure for an ORL message with a trigger event of - General Laboratory Order Acknowledgment Message (Patient Optional) (O53)
  ORL_O54http://terminology.hl7.org/CodeSystem/v2-0354O54Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message – Multiple Order Per Specimen (Patient Optional) (O54)
  ORL_O55http://terminology.hl7.org/CodeSystem/v2-0354O55Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message – Multiple Order Per Container of Specimen (Patient Optional) (O55)
  ORL_O56http://terminology.hl7.org/CodeSystem/v2-0354O56Identifier for the message structure for an ORL message with a trigger event of Specimen Shipment Centric Laboratory Order Acknowledgment Message (Patient Optional) (O56)
  ORM_O01http://terminology.hl7.org/CodeSystem/v2-0354O01O01
  ORN_O08http://terminology.hl7.org/CodeSystem/v2-0354O08O08
  ORP_O10http://terminology.hl7.org/CodeSystem/v2-0354O10O10
  ORR_O02http://terminology.hl7.org/CodeSystem/v2-0354O02O02
  RDE_O01http://terminology.hl7.org/CodeSystem/v2-0354O01O01
  ORS_O06http://terminology.hl7.org/CodeSystem/v2-0354O06O06
  ORU_R01http://terminology.hl7.org/CodeSystem/v2-0354R01R01
  ORU_R30http://terminology.hl7.org/CodeSystem/v2-0354R30R30
  ORU_W01http://terminology.hl7.org/CodeSystem/v2-0354W01W01
  ORX_O43http://terminology.hl7.org/CodeSystem/v2-0354O43O43
  ORX_O58http://terminology.hl7.org/CodeSystem/v2-0354O58Identifier for the message structure for an ORX message with a trigger event of General Order Message with Document Payload Acknowledgement Message (O58)
  OSM_R26http://terminology.hl7.org/CodeSystem/v2-0354R26R26
  OSQ_Q06http://terminology.hl7.org/CodeSystem/v2-0354Q06Q06
  OSR_Q06http://terminology.hl7.org/CodeSystem/v2-0354Q06Q06
  OSU_O41http://terminology.hl7.org/CodeSystem/v2-0354O41O41
  OSU_O51http://terminology.hl7.org/CodeSystem/v2-0354O51Identifier for the message structure for an OSU message with a trigger event of Order Status Update (O51)
  OSU_O52http://terminology.hl7.org/CodeSystem/v2-0354O52Identifier for the message structure for an OSU message with a trigger event of Order Status Update Acknowledgement (O52)
  OUL_R21http://terminology.hl7.org/CodeSystem/v2-0354R21R21
  OUL_R22http://terminology.hl7.org/CodeSystem/v2-0354R22R22
  OUL_R23http://terminology.hl7.org/CodeSystem/v2-0354R23R23
  OUL_R24http://terminology.hl7.org/CodeSystem/v2-0354R24R24
  PEX_P07http://terminology.hl7.org/CodeSystem/v2-0354P07, P08P07, P08
  PGL_PC6http://terminology.hl7.org/CodeSystem/v2-0354PC6, PC7, PC8PC6, PC7, PC8
  PMU_B01http://terminology.hl7.org/CodeSystem/v2-0354B01, B02B01, B02
  RQQ_Q09http://terminology.hl7.org/CodeSystem/v2-0354Q09Q09
  RRA_O02http://terminology.hl7.org/CodeSystem/v2-0354O02O02
  PMU_B03http://terminology.hl7.org/CodeSystem/v2-0354B03B03
  PMU_B04http://terminology.hl7.org/CodeSystem/v2-0354B04, B05, B06B04, B05, B06
  PMU_B07http://terminology.hl7.org/CodeSystem/v2-0354B07B07
  PMU_B08http://terminology.hl7.org/CodeSystem/v2-0354B08B08
  PPG_PCGhttp://terminology.hl7.org/CodeSystem/v2-0354PCC, PCG, PCH, PCJPCC, PCG, PCH, PCJ
  PPP_PCBhttp://terminology.hl7.org/CodeSystem/v2-0354PCB, PCDPCB, PCD
  PPR_PC1http://terminology.hl7.org/CodeSystem/v2-0354PC1, PC2, PC3PC1, PC2, PC3
  PPT_PCLhttp://terminology.hl7.org/CodeSystem/v2-0354PCLPCL
  PPV_PCAhttp://terminology.hl7.org/CodeSystem/v2-0354PCAPCA
  PRR_PC5http://terminology.hl7.org/CodeSystem/v2-0354PC5PC5
  PTR_PCFhttp://terminology.hl7.org/CodeSystem/v2-0354PCFPCF
  QBP_E03http://terminology.hl7.org/CodeSystem/v2-0354E03E03
  QBP_E22http://terminology.hl7.org/CodeSystem/v2-0354E22E22
  QBP_O33http://terminology.hl7.org/CodeSystem/v2-0354O33O33
  QBP_O34http://terminology.hl7.org/CodeSystem/v2-0354O34O34
  SPQ_Q08http://terminology.hl7.org/CodeSystem/v2-0354Q08Q08
  QBP_Q11http://terminology.hl7.org/CodeSystem/v2-0354Q11Q11
  RDY_K11http://terminology.hl7.org/CodeSystem/v2-0354K11K11
  QBP_Q13http://terminology.hl7.org/CodeSystem/v2-0354Q13Q13
  QBP_Q15http://terminology.hl7.org/CodeSystem/v2-0354Q15Q15
  QBP_Q21http://terminology.hl7.org/CodeSystem/v2-0354Q21, Q22, Q23,Q24, Q25Q21, Q22, Q23,Q24, Q25
  QCK_Q02http://terminology.hl7.org/CodeSystem/v2-0354Q02Q02
  QCN_J01http://terminology.hl7.org/CodeSystem/v2-0354J01, J02J01, J02
  RSP_K24http://terminology.hl7.org/CodeSystem/v2-0354K24K24
  QRF_W02http://terminology.hl7.org/CodeSystem/v2-0354W02W02
  QRY_A19http://terminology.hl7.org/CodeSystem/v2-0354A19A19
  QRY_PC4http://terminology.hl7.org/CodeSystem/v2-0354PC4, PC9, PCE, PCKPC4, PC9, PCE, PCK
  TBR_R08http://terminology.hl7.org/CodeSystem/v2-0354R08R08
  QRY_Q01http://terminology.hl7.org/CodeSystem/v2-0354Q01, Q26, Q27, Q28, Q29, Q30Q01, Q26, Q27, Q28, Q29, Q30
  TBR_R09http://terminology.hl7.org/CodeSystem/v2-0354R09R09
  QRY_Q02http://terminology.hl7.org/CodeSystem/v2-0354Q02Q02
  QRY_R02http://terminology.hl7.org/CodeSystem/v2-0354R02R02
  QRY_T12http://terminology.hl7.org/CodeSystem/v2-0354T12T12
  VQQ_Q07http://terminology.hl7.org/CodeSystem/v2-0354Q07Q07
  QSB_Q16http://terminology.hl7.org/CodeSystem/v2-0354Q16Q16
  QVR_Q17http://terminology.hl7.org/CodeSystem/v2-0354Q17Q17
  RAR_RARhttp://terminology.hl7.org/CodeSystem/v2-0354RARRAR
  RAS_O17http://terminology.hl7.org/CodeSystem/v2-0354O17O17
  RCI_I05http://terminology.hl7.org/CodeSystem/v2-0354I05I05
  RCL_I06http://terminology.hl7.org/CodeSystem/v2-0354I06I06
  RDE_O11http://terminology.hl7.org/CodeSystem/v2-0354O11, O25O11, O25
  RDE_O49http://terminology.hl7.org/CodeSystem/v2-0354Events O49O49
  RDR_RDRhttp://terminology.hl7.org/CodeSystem/v2-0354RDRRDR
  RDS_O13http://terminology.hl7.org/CodeSystem/v2-0354O13O13
  RDY_K15http://terminology.hl7.org/CodeSystem/v2-0354K15K15
  REF_I12http://terminology.hl7.org/CodeSystem/v2-0354I12, I13, I14, I15I12, I13, I14, I15
  RER_RERhttp://terminology.hl7.org/CodeSystem/v2-0354RERRER
  RGR_RGRhttp://terminology.hl7.org/CodeSystem/v2-0354RGRRGR
  RGV_O15http://terminology.hl7.org/CodeSystem/v2-0354O15O15
  ROR_RORhttp://terminology.hl7.org/CodeSystem/v2-0354RORROR
  RPA_I08http://terminology.hl7.org/CodeSystem/v2-0354I08, I09. I10, I11I08, I09. I10, I11
  RPI_I01http://terminology.hl7.org/CodeSystem/v2-0354I01, I04I01, I04
  RPI_I04http://terminology.hl7.org/CodeSystem/v2-0354I04I04
  RPL_I02http://terminology.hl7.org/CodeSystem/v2-0354I02I02
  RPR_I03http://terminology.hl7.org/CodeSystem/v2-0354I03I03
  RQA_I08http://terminology.hl7.org/CodeSystem/v2-0354I08, I09, I10, I11I08, I09, I10, I11
  RQC_I05http://terminology.hl7.org/CodeSystem/v2-0354I05, I06I05, I06
  RQI_I01http://terminology.hl7.org/CodeSystem/v2-0354I01, I02, I03, I07I01, I02, I03, I07
  RQP_I04http://terminology.hl7.org/CodeSystem/v2-0354I04I04
  RRA_O18http://terminology.hl7.org/CodeSystem/v2-0354O18O18
  RRD_O14http://terminology.hl7.org/CodeSystem/v2-0354O14O14
  RRE_O12http://terminology.hl7.org/CodeSystem/v2-0354O12, O26O12, O26
  RRE_O50http://terminology.hl7.org/CodeSystem/v2-0354Events O50O50
  RRG_O16http://terminology.hl7.org/CodeSystem/v2-0354O16O16
  RRI_I12http://terminology.hl7.org/CodeSystem/v2-0354I12, I13, I14, I15I12, I13, I14, I15
  RSP_E03http://terminology.hl7.org/CodeSystem/v2-0354E03E03
  RSP_E22http://terminology.hl7.org/CodeSystem/v2-0354E22E22
  RSP_K11http://terminology.hl7.org/CodeSystem/v2-0354K11K11
  RSP_K21http://terminology.hl7.org/CodeSystem/v2-0354K21K21
  RSP_K22http://terminology.hl7.org/CodeSystem/v2-0354K22K22
  RSP_K23http://terminology.hl7.org/CodeSystem/v2-0354K23, K24K23, K24
  RSP_K25http://terminology.hl7.org/CodeSystem/v2-0354K25K25
  RSP_K31http://terminology.hl7.org/CodeSystem/v2-0354K31K31
  RSP_K32http://terminology.hl7.org/CodeSystem/v2-0354K32K32
  RSP_O33http://terminology.hl7.org/CodeSystem/v2-0354O33O33
  RSP_O34http://terminology.hl7.org/CodeSystem/v2-0354O34O34
  RSP_Q11http://terminology.hl7.org/CodeSystem/v2-0354Q11Q11
  RTB_K13http://terminology.hl7.org/CodeSystem/v2-0354K13K13
  SDR_S31http://terminology.hl7.org/CodeSystem/v2-0354S31, S36S31, S36
  SDR_S32http://terminology.hl7.org/CodeSystem/v2-0354S32, S37S32, S37
  SET_S38http://terminology.hl7.org/CodeSystem/v2-0354Specimen Container Preparation and Specimen Collection EventThis message structure supports tracking of information related to preparations for specimen collection and the collection event.
  SET_S40http://terminology.hl7.org/CodeSystem/v2-0354Specimen Collection Event unsuccessfulThis message structure supports tracking of information when specimen collection is not successful.
  SET_S41http://terminology.hl7.org/CodeSystem/v2-0354Specimen Movement EventThis message structure supports tracking of information related to the movements of specimens across locations, and placement in and out of storage.
  SET_S45http://terminology.hl7.org/CodeSystem/v2-0354Specimen Identification EventsThis message structure supports tracking of information to identify or de-identify specimens or at time of final disposal.
  SET_S50http://terminology.hl7.org/CodeSystem/v2-0354Specimen Procedure Step successfulThis message structure supports tracking of information related to processing of one or more specimen that may result in derived (child) specimen or not.
  SET_S52http://terminology.hl7.org/CodeSystem/v2-0354Specimen Procedure Step unsuccessfulThis message structure supports tracking of information when the processing of a specimen was unsuccessful.
  SIU_S12http://terminology.hl7.org/CodeSystem/v2-0354S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S26S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S26
  SLR_S28http://terminology.hl7.org/CodeSystem/v2-0354S28, S29, S30, S34, S35S28, S29, S30, S34, S35
  SQM_S25http://terminology.hl7.org/CodeSystem/v2-0354S25S25
  SQR_S25http://terminology.hl7.org/CodeSystem/v2-0354S25S25
  SRM_S01http://terminology.hl7.org/CodeSystem/v2-0354S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11
  SRR_S01http://terminology.hl7.org/CodeSystem/v2-0354S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11
  QBP_Z73http://terminology.hl7.org/CodeSystem/v2-0354Z73Z73
  SSR_U04http://terminology.hl7.org/CodeSystem/v2-0354U04U04
  RSP_Z82http://terminology.hl7.org/CodeSystem/v2-0354Z82Z82
  SSU_U03http://terminology.hl7.org/CodeSystem/v2-0354U03U03
  RSP_Z86http://terminology.hl7.org/CodeSystem/v2-0354Z86Z86
  STC_S33http://terminology.hl7.org/CodeSystem/v2-0354S33S33
  RSP_Z88http://terminology.hl7.org/CodeSystem/v2-0354Z88Z88
  SUR_P09http://terminology.hl7.org/CodeSystem/v2-0354P09P09
  RSP_Z90http://terminology.hl7.org/CodeSystem/v2-0354Z90Z90
  TCU_U10http://terminology.hl7.org/CodeSystem/v2-0354U10, U11U10, U11
  RTB_Knnhttp://terminology.hl7.org/CodeSystem/v2-0354KnnKnn
  UDM_Q05http://terminology.hl7.org/CodeSystem/v2-0354Q05Q05
  RTB_Z74http://terminology.hl7.org/CodeSystem/v2-0354Z74Z74
  VXQ_V01http://terminology.hl7.org/CodeSystem/v2-0354V01V01
  QBP_Qnnhttp://terminology.hl7.org/CodeSystem/v2-0354QnnQnn
  VXR_V03http://terminology.hl7.org/CodeSystem/v2-0354V03V03
  VXU_V04http://terminology.hl7.org/CodeSystem/v2-0354V04V04
  VXX_V02http://terminology.hl7.org/CodeSystem/v2-0354V02V02

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code