Valueset-resource-types.xml

Definition for Value SetResourceType

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="resource-types"/>
  <meta>
    <lastUpdated value="2015-10-24T07:41:03.495+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>ResourceType</h2>
      <p>One of the resource types defined as part of FHIR.</p>
      <p>This value set has an inline code system http://hl7.org/fhir/resource-types, which defines
         the following codes:</p>
      <table class="codes">
        <tr>
          <td>
            <b>Code</b>
          </td>
          <td>
            <b>Display</b>
          </td>
          <td>
            <b>Definition</b>
          </td>
        </tr>
        <tr>
          <td>Account
            <a name="Account"> </a>
          </td>
          <td>Account</td>
          <td>A financial tool for tracking value accrued for a particular purpose.  In the healthcare
             field, used to track charges for a patient, cost centres, etc.</td>
        </tr>
        <tr>
          <td>AllergyIntolerance
            <a name="AllergyIntolerance"> </a>
          </td>
          <td>AllergyIntolerance</td>
          <td>Risk of harmful or undesirable, physiological response which is unique to an individual
             and associated with exposure to a substance.</td>
        </tr>
        <tr>
          <td>Appointment
            <a name="Appointment"> </a>
          </td>
          <td>Appointment</td>
          <td>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).</td>
        </tr>
        <tr>
          <td>AppointmentResponse
            <a name="AppointmentResponse"> </a>
          </td>
          <td>AppointmentResponse</td>
          <td>A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation
             or rejection.</td>
        </tr>
        <tr>
          <td>AuditEvent
            <a name="AuditEvent"> </a>
          </td>
          <td>AuditEvent</td>
          <td>A record of an event made for purposes of maintaining a security log. Typical uses include
             detection of intrusion attempts and monitoring for inappropriate usage.</td>
        </tr>
        <tr>
          <td>Basic
            <a name="Basic"> </a>
          </td>
          <td>Basic</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Binary
            <a name="Binary"> </a>
          </td>
          <td>Binary</td>
          <td>A binary resource can contain any content, whether text, image, pdf, zip archive, etc.</td>
        </tr>
        <tr>
          <td>BodySite
            <a name="BodySite"> </a>
          </td>
          <td>BodySite</td>
          <td>Record details about the anatomical location of a specimen or body part.  This resource
             may be used when a coded concept does not provide the necessary detail needed for the
             use case.</td>
        </tr>
        <tr>
          <td>Bundle
            <a name="Bundle"> </a>
          </td>
          <td>Bundle</td>
          <td>A container for a collection of resources.</td>
        </tr>
        <tr>
          <td>CarePlan
            <a name="CarePlan"> </a>
          </td>
          <td>CarePlan</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Claim
            <a name="Claim"> </a>
          </td>
          <td>Claim</td>
          <td>A provider issued list of services and products provided, or to be provided, to a patient
             which is provided to an insurer for payment recovery.</td>
        </tr>
        <tr>
          <td>ClaimResponse
            <a name="ClaimResponse"> </a>
          </td>
          <td>ClaimResponse</td>
          <td>This resource provides the adjudication details from the processing of a Claim resource.</td>
        </tr>
        <tr>
          <td>ClinicalImpression
            <a name="ClinicalImpression"> </a>
          </td>
          <td>ClinicalImpression</td>
          <td>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 &quot;ClinicalI
            mpression&quot; rather than &quot;ClinicalAssessment&quot; to avoid confusion with the
             recording of assessment tools such as Apgar score.</td>
        </tr>
        <tr>
          <td>Communication
            <a name="Communication"> </a>
          </td>
          <td>Communication</td>
          <td>An occurrence of information being transmitted; e.g. an alert that was sent to a responsible
             provider, a public health agency was notified about a reportable condition.</td>
        </tr>
        <tr>
          <td>CommunicationRequest
            <a name="CommunicationRequest"> </a>
          </td>
          <td>CommunicationRequest</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Composition
            <a name="Composition"> </a>
          </td>
          <td>Composition</td>
          <td>A set of healthcare-related information that is assembled together into a single logical
             document 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. While a
             Composition defines the structure, it does not actually contain the content: rather the
             full content of a document is contained in a Bundle, of which the Composition is the first
             resource contained.</td>
        </tr>
        <tr>
          <td>ConceptMap
            <a name="ConceptMap"> </a>
          </td>
          <td>ConceptMap</td>
          <td>A statement of relationships from one set of concepts to one or more other concepts -
             either code systems or data elements, or classes in class models.</td>
        </tr>
        <tr>
          <td>Condition
            <a name="Condition"> </a>
          </td>
          <td>Condition</td>
          <td>Use to record detailed information about conditions, problems or diagnoses recognized
             by a clinician. There are many uses including: recording a diagnosis during an encounter;
             populating a problem list or a summary statement, such as a discharge summary.</td>
        </tr>
        <tr>
          <td>Conformance
            <a name="Conformance"> </a>
          </td>
          <td>Conformance</td>
          <td>A conformance statement is a set of capabilities of a FHIR Server that may be used as
             a statement of actual server functionality or a statement of required or desired server
             implementation.</td>
        </tr>
        <tr>
          <td>Contract
            <a name="Contract"> </a>
          </td>
          <td>Contract</td>
          <td>A formal agreement between parties regarding the conduct of business, exchange of information
             or other matters.</td>
        </tr>
        <tr>
          <td>Coverage
            <a name="Coverage"> </a>
          </td>
          <td>Coverage</td>
          <td>Financial instrument which may be used to pay for or reimburse health care products and
             services.</td>
        </tr>
        <tr>
          <td>DataElement
            <a name="DataElement"> </a>
          </td>
          <td>DataElement</td>
          <td>The formal description of a single piece of information that can be gathered and reported.</td>
        </tr>
        <tr>
          <td>DetectedIssue
            <a name="DetectedIssue"> </a>
          </td>
          <td>DetectedIssue</td>
          <td>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, etc.</td>
        </tr>
        <tr>
          <td>Device
            <a name="Device"> </a>
          </td>
          <td>Device</td>
          <td>This resource identifies an instance of a manufactured item that is used in the provision
             of healthcare without being substantially changed through that activity. The device may
             be a medical or non-medical device.  Medical devices includes durable (reusable) medical
             equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment,
             and research for healthcare and public health.  Non-medical devices may include items
             such as a machine, cellphone, computer, application, etc.</td>
        </tr>
        <tr>
          <td>DeviceComponent
            <a name="DeviceComponent"> </a>
          </td>
          <td>DeviceComponent</td>
          <td>Describes the characteristics, operational status and capabilities of a medical-related
             component of a medical device.</td>
        </tr>
        <tr>
          <td>DeviceMetric
            <a name="DeviceMetric"> </a>
          </td>
          <td>DeviceMetric</td>
          <td>Describes a measurement, calculation or setting capability of a medical device.</td>
        </tr>
        <tr>
          <td>DeviceUseRequest
            <a name="DeviceUseRequest"> </a>
          </td>
          <td>DeviceUseRequest</td>
          <td>Represents a request for a patient to employ a medical device. The device may be an implantable
             device, or an external assistive device, such as a walker.</td>
        </tr>
        <tr>
          <td>DeviceUseStatement
            <a name="DeviceUseStatement"> </a>
          </td>
          <td>DeviceUseStatement</td>
          <td>A record of a device being used by a patient where the record is the result of a report
             from the patient or another clinician.</td>
        </tr>
        <tr>
          <td>DiagnosticOrder
            <a name="DiagnosticOrder"> </a>
          </td>
          <td>DiagnosticOrder</td>
          <td>A record of a request for a diagnostic investigation service to be performed.</td>
        </tr>
        <tr>
          <td>DiagnosticReport
            <a name="DiagnosticReport"> </a>
          </td>
          <td>DiagnosticReport</td>
          <td>The findings and interpretation of diagnostic  tests performed on patients, groups of
             patients, devices, and locations, and/or specimens derived from these. The report includes
             clinical context such as requesting and provider information, and some mix of atomic results,
             images, textual and coded interpretations, and formatted representation of diagnostic
             reports.</td>
        </tr>
        <tr>
          <td>DocumentManifest
            <a name="DocumentManifest"> </a>
          </td>
          <td>DocumentManifest</td>
          <td>A manifest that defines a set of documents.</td>
        </tr>
        <tr>
          <td>DocumentReference
            <a name="DocumentReference"> </a>
          </td>
          <td>DocumentReference</td>
          <td>A reference to a document .</td>
        </tr>
        <tr>
          <td>DomainResource
            <a name="DomainResource"> </a>
          </td>
          <td>DomainResource</td>
          <td>--- Abstract Type! ---A resource that includes narrative, extensions, and contained resources.</td>
        </tr>
        <tr>
          <td>EligibilityRequest
            <a name="EligibilityRequest"> </a>
          </td>
          <td>EligibilityRequest</td>
          <td>This resource provides the insurance eligibility details from the insurer regarding a
             specified coverage and optionally some class of service.</td>
        </tr>
        <tr>
          <td>EligibilityResponse
            <a name="EligibilityResponse"> </a>
          </td>
          <td>EligibilityResponse</td>
          <td>This resource provides eligibility and plan details from the processing of an Eligibility
             resource.</td>
        </tr>
        <tr>
          <td>Encounter
            <a name="Encounter"> </a>
          </td>
          <td>Encounter</td>
          <td>An interaction between a patient and healthcare provider(s) for the purpose of providing
             healthcare service(s) or assessing the health status of a patient.</td>
        </tr>
        <tr>
          <td>EnrollmentRequest
            <a name="EnrollmentRequest"> </a>
          </td>
          <td>EnrollmentRequest</td>
          <td>This resource provides the insurance enrollment details to the insurer regarding a specified
             coverage.</td>
        </tr>
        <tr>
          <td>EnrollmentResponse
            <a name="EnrollmentResponse"> </a>
          </td>
          <td>EnrollmentResponse</td>
          <td>This resource provides enrollment and plan details from the processing of an Enrollment
             resource.</td>
        </tr>
        <tr>
          <td>EpisodeOfCare
            <a name="EpisodeOfCare"> </a>
          </td>
          <td>EpisodeOfCare</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>ExplanationOfBenefit
            <a name="ExplanationOfBenefit"> </a>
          </td>
          <td>ExplanationOfBenefit</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>FamilyMemberHistory
            <a name="FamilyMemberHistory"> </a>
          </td>
          <td>FamilyMemberHistory</td>
          <td>Significant health events and conditions for a person related to the patient relevant
             in the context of care for the patient.</td>
        </tr>
        <tr>
          <td>Flag
            <a name="Flag"> </a>
          </td>
          <td>Flag</td>
          <td>Prospective warnings of potential issues when providing care to the patient.</td>
        </tr>
        <tr>
          <td>Goal
            <a name="Goal"> </a>
          </td>
          <td>Goal</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Group
            <a name="Group"> </a>
          </td>
          <td>Group</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>HealthcareService
            <a name="HealthcareService"> </a>
          </td>
          <td>HealthcareService</td>
          <td>The details of a healthcare service available at a location.</td>
        </tr>
        <tr>
          <td>ImagingObjectSelection
            <a name="ImagingObjectSelection"> </a>
          </td>
          <td>ImagingObjectSelection</td>
          <td>A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances).  The referenced
             SOP Instances (images or other content) are for a single patient, and may be from one
             or more studies. The referenced SOP Instances have been selected for a purpose, such as
             quality assurance, conference, or consult. Reflecting that range of purposes, typical
             ImagingObjectSelection resources may include all SOP Instances in a study (perhaps for
             sharing through a Health Information Exchange); key images from multiple studies (for
             reference by a referring or treating physician); a multi-frame ultrasound instance (&quot;cine&quot;
             video clip) and a set of measurements taken from that instance (for inclusion in a teaching
             file); and so on.</td>
        </tr>
        <tr>
          <td>ImagingStudy
            <a name="ImagingStudy"> </a>
          </td>
          <td>ImagingStudy</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Immunization
            <a name="Immunization"> </a>
          </td>
          <td>Immunization</td>
          <td>Describes the event of a patient being administered a vaccination or a record of a vaccination
             as reported by a patient, a clinician or another party and may include vaccine reaction
             information and what vaccination protocol was followed.</td>
        </tr>
        <tr>
          <td>ImmunizationRecommendation
            <a name="ImmunizationRecommendation"> </a>
          </td>
          <td>ImmunizationRecommendation</td>
          <td>A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's
             immunization eligibility according to a published schedule) with optional supporting justification.</td>
        </tr>
        <tr>
          <td>ImplementationGuide
            <a name="ImplementationGuide"> </a>
          </td>
          <td>ImplementationGuide</td>
          <td>A set of rules or how FHIR is used to solve a particular problem. 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.</td>
        </tr>
        <tr>
          <td>List
            <a name="List"> </a>
          </td>
          <td>List</td>
          <td>A set of information summarized from a list of other resources.</td>
        </tr>
        <tr>
          <td>Location
            <a name="Location"> </a>
          </td>
          <td>Location</td>
          <td>Details and position information for a physical place where services are provided  and
             resources and participants may be stored, found, contained or accommodated.</td>
        </tr>
        <tr>
          <td>Media
            <a name="Media"> </a>
          </td>
          <td>Media</td>
          <td>A photo, video, or audio recording acquired or used in healthcare. The actual content
             may be inline or provided by direct reference.</td>
        </tr>
        <tr>
          <td>Medication
            <a name="Medication"> </a>
          </td>
          <td>Medication</td>
          <td>This resource is primarily used for the identification and definition of a medication.
             It covers the ingredients and the packaging for a medication.</td>
        </tr>
        <tr>
          <td>MedicationAdministration
            <a name="MedicationAdministration"> </a>
          </td>
          <td>MedicationAdministration</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>MedicationDispense
            <a name="MedicationDispense"> </a>
          </td>
          <td>MedicationDispense</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>MedicationOrder
            <a name="MedicationOrder"> </a>
          </td>
          <td>MedicationOrder</td>
          <td>An order for both supply of the medication and the instructions for administration of
             the medication to a patient. The resource is called &quot;MedicationOrder&quot; rather
             than &quot;MedicationPrescription&quot; to generalize the use across inpatient and outpatient
             settings as well as for care plans, etc.</td>
        </tr>
        <tr>
          <td>MedicationStatement
            <a name="MedicationStatement"> </a>
          </td>
          <td>MedicationStatement</td>
          <td>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 e.g. 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 medication statement and a medication administration
             is that the medication administration has complete administration information and is based
             on actual administration information from the person who administered the medication.
              A medication statement 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.</td>
        </tr>
        <tr>
          <td>MessageHeader
            <a name="MessageHeader"> </a>
          </td>
          <td>MessageHeader</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>NamingSystem
            <a name="NamingSystem"> </a>
          </td>
          <td>NamingSystem</td>
          <td>A curated namespace that issues unique symbols within that namespace for the identification
             of concepts, people, devices, etc.  Represents a &quot;System&quot; used within the Identifier
             and Coding data types.</td>
        </tr>
        <tr>
          <td>NutritionOrder
            <a name="NutritionOrder"> </a>
          </td>
          <td>NutritionOrder</td>
          <td>A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to
             a patient/resident.</td>
        </tr>
        <tr>
          <td>Observation
            <a name="Observation"> </a>
          </td>
          <td>Observation</td>
          <td>Measurements and simple assertions made about a patient, device or other subject.</td>
        </tr>
        <tr>
          <td>OperationDefinition
            <a name="OperationDefinition"> </a>
          </td>
          <td>OperationDefinition</td>
          <td>A formal computable definition of an operation (on the RESTful interface) or a named query
             (using the search interaction).</td>
        </tr>
        <tr>
          <td>OperationOutcome
            <a name="OperationOutcome"> </a>
          </td>
          <td>OperationOutcome</td>
          <td>A collection of error, warning or information messages that result from a system action.</td>
        </tr>
        <tr>
          <td>Order
            <a name="Order"> </a>
          </td>
          <td>Order</td>
          <td>A request to perform an action.</td>
        </tr>
        <tr>
          <td>OrderResponse
            <a name="OrderResponse"> </a>
          </td>
          <td>OrderResponse</td>
          <td>A response to an order.</td>
        </tr>
        <tr>
          <td>Organization
            <a name="Organization"> </a>
          </td>
          <td>Organization</td>
          <td>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, etc.</td>
        </tr>
        <tr>
          <td>Parameters
            <a name="Parameters"> </a>
          </td>
          <td>Parameters</td>
          <td>This special resource type is used to represent an operation request and response (operations.html).
             It has no other use, and there is no RESTful endpoint associated with it.</td>
        </tr>
        <tr>
          <td>Patient
            <a name="Patient"> </a>
          </td>
          <td>Patient</td>
          <td>Demographics and other administrative information about an individual or animal receiving
             care or other health-related services.</td>
        </tr>
        <tr>
          <td>PaymentNotice
            <a name="PaymentNotice"> </a>
          </td>
          <td>PaymentNotice</td>
          <td>This resource provides the status of the payment for goods and services rendered, and
             the request and response resource references.</td>
        </tr>
        <tr>
          <td>PaymentReconciliation
            <a name="PaymentReconciliation"> </a>
          </td>
          <td>PaymentReconciliation</td>
          <td>This resource provides payment details and claim references supporting a bulk payment.</td>
        </tr>
        <tr>
          <td>Person
            <a name="Person"> </a>
          </td>
          <td>Person</td>
          <td>Demographics and administrative information about a person independent of a specific health-related
             context.</td>
        </tr>
        <tr>
          <td>Practitioner
            <a name="Practitioner"> </a>
          </td>
          <td>Practitioner</td>
          <td>A person who is directly or indirectly involved in the provisioning of healthcare.</td>
        </tr>
        <tr>
          <td>Procedure
            <a name="Procedure"> </a>
          </td>
          <td>Procedure</td>
          <td>An action that is or was performed on a patient. This can be a physical intervention like
             an operation, or less invasive like counseling or hypnotherapy.</td>
        </tr>
        <tr>
          <td>ProcedureRequest
            <a name="ProcedureRequest"> </a>
          </td>
          <td>ProcedureRequest</td>
          <td>A request for a procedure to be performed. May be a proposal or an order.</td>
        </tr>
        <tr>
          <td>ProcessRequest
            <a name="ProcessRequest"> </a>
          </td>
          <td>ProcessRequest</td>
          <td>This resource provides the target, request and response, and action details for an action
             to be performed by the target on or about existing resources.</td>
        </tr>
        <tr>
          <td>ProcessResponse
            <a name="ProcessResponse"> </a>
          </td>
          <td>ProcessResponse</td>
          <td>This resource provides processing status, errors and notes from the processing of a resource.</td>
        </tr>
        <tr>
          <td>Provenance
            <a name="Provenance"> </a>
          </td>
          <td>Provenance</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Questionnaire
            <a name="Questionnaire"> </a>
          </td>
          <td>Questionnaire</td>
          <td>A structured set of questions intended to guide the collection of answers. The questions
             are ordered and grouped into coherent subsets, corresponding to the structure of the grouping
             of the underlying questions.</td>
        </tr>
        <tr>
          <td>QuestionnaireResponse
            <a name="QuestionnaireResponse"> </a>
          </td>
          <td>QuestionnaireResponse</td>
          <td>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 underlying
             questions.</td>
        </tr>
        <tr>
          <td>ReferralRequest
            <a name="ReferralRequest"> </a>
          </td>
          <td>ReferralRequest</td>
          <td>Used to record and send details about a request for referral service or transfer of a
             patient to the care of another provider or provider organization.</td>
        </tr>
        <tr>
          <td>RelatedPerson
            <a name="RelatedPerson"> </a>
          </td>
          <td>RelatedPerson</td>
          <td>Information about a person that is involved in the care for a patient, but who is not
             the target of healthcare, nor has a formal responsibility in the care process.</td>
        </tr>
        <tr>
          <td>Resource
            <a name="Resource"> </a>
          </td>
          <td>Resource</td>
          <td>--- Abstract Type! ---This is the base resource type for everything.</td>
        </tr>
        <tr>
          <td>RiskAssessment
            <a name="RiskAssessment"> </a>
          </td>
          <td>RiskAssessment</td>
          <td>An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood
             of each outcome.</td>
        </tr>
        <tr>
          <td>Schedule
            <a name="Schedule"> </a>
          </td>
          <td>Schedule</td>
          <td>A container for slot(s) of time that may be available for booking appointments.</td>
        </tr>
        <tr>
          <td>SearchParameter
            <a name="SearchParameter"> </a>
          </td>
          <td>SearchParameter</td>
          <td>A search parameter that defines a named search item that can be used to search/filter
             on a resource.</td>
        </tr>
        <tr>
          <td>Slot
            <a name="Slot"> </a>
          </td>
          <td>Slot</td>
          <td>A slot of time on a schedule that may be available for booking appointments.</td>
        </tr>
        <tr>
          <td>Specimen
            <a name="Specimen"> </a>
          </td>
          <td>Specimen</td>
          <td>A sample to be used for analysis.</td>
        </tr>
        <tr>
          <td>StructureDefinition
            <a name="StructureDefinition"> </a>
          </td>
          <td>StructureDefinition</td>
          <td>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.</td>
        </tr>
        <tr>
          <td>Subscription
            <a name="Subscription"> </a>
          </td>
          <td>Subscription</td>
          <td>The subscription resource is used to define a push based subscription from a server to
             another system. Once a subscription is registered with the server, the server checks every
             resource that is created or updated, and if the resource matches the given criteria, it
             sends a message on the defined &quot;channel&quot; so that another system is able to take
             an appropriate action.</td>
        </tr>
        <tr>
          <td>Substance
            <a name="Substance"> </a>
          </td>
          <td>Substance</td>
          <td>A homogeneous material with a definite composition.</td>
        </tr>
        <tr>
          <td>SupplyDelivery
            <a name="SupplyDelivery"> </a>
          </td>
          <td>SupplyDelivery</td>
          <td>Record of delivery of what is supplied.</td>
        </tr>
        <tr>
          <td>SupplyRequest
            <a name="SupplyRequest"> </a>
          </td>
          <td>SupplyRequest</td>
          <td>A record of a request for a medication, substance or device used in the healthcare setting.</td>
        </tr>
        <tr>
          <td>TestScript
            <a name="TestScript"> </a>
          </td>
          <td>TestScript</td>
          <td>TestScript is a resource that specifies a suite of tests against a FHIR server implementation
             to determine compliance against the FHIR specification.</td>
        </tr>
        <tr>
          <td>ValueSet
            <a name="ValueSet"> </a>
          </td>
          <td>ValueSet</td>
          <td>A value set specifies a set of codes drawn from one or more code systems.</td>
        </tr>
        <tr>
          <td>VisionPrescription
            <a name="VisionPrescription"> </a>
          </td>
          <td>VisionPrescription</td>
          <td>An authorization for the supply of glasses and/or contact lenses to a patient.</td>
        </tr>
      </table>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.4.642.2.16"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/resource-types"/>
  <version value="1.0.2"/>
  <name value="ResourceType"/>
  <status value="draft"/>
  <experimental value="false"/>
  <publisher value="HL7 (FHIR Project)"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="fhir@lists.hl7.org"/>
    </telecom>
  </contact>
  <date value="2015-10-24T07:41:03+11:00"/>
  <description value="One of the resource types defined as part of FHIR."/>
  <codeSystem>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
      <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.16"/>
    </extension>
    <system value="http://hl7.org/fhir/resource-types"/>
    <version value="1.0.2"/>
    <caseSensitive value="true"/>
    <concept>
      <code value="Account"/>
      <display value="Account"/>
      <definition value="A financial tool for tracking value accrued for a particular purpose.  In the healthcare
       field, used to track charges for a patient, cost centres, etc."/>
    </concept>
    <concept>
      <code value="AllergyIntolerance"/>
      <display value="AllergyIntolerance"/>
      <definition value="Risk of harmful or undesirable, physiological response which is unique to an individual
       and associated with exposure to a substance."/>
    </concept>
    <concept>
      <code value="Appointment"/>
      <display value="Appointment"/>
      <definition value="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)."/>
    </concept>
    <concept>
      <code value="AppointmentResponse"/>
      <display value="AppointmentResponse"/>
      <definition value="A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation
       or rejection."/>
    </concept>
    <concept>
      <code value="AuditEvent"/>
      <display value="AuditEvent"/>
      <definition value="A record of an event made for purposes of maintaining a security log. Typical uses include
       detection of intrusion attempts and monitoring for inappropriate usage."/>
    </concept>
    <concept>
      <code value="Basic"/>
      <display value="Basic"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Binary"/>
      <display value="Binary"/>
      <definition value="A binary resource can contain any content, whether text, image, pdf, zip archive, etc."/>
    </concept>
    <concept>
      <code value="BodySite"/>
      <display value="BodySite"/>
      <definition value="Record details about the anatomical location of a specimen or body part.  This resource
       may be used when a coded concept does not provide the necessary detail needed for the
       use case."/>
    </concept>
    <concept>
      <code value="Bundle"/>
      <display value="Bundle"/>
      <definition value="A container for a collection of resources."/>
    </concept>
    <concept>
      <code value="CarePlan"/>
      <display value="CarePlan"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Claim"/>
      <display value="Claim"/>
      <definition value="A provider issued list of services and products provided, or to be provided, to a patient
       which is provided to an insurer for payment recovery."/>
    </concept>
    <concept>
      <code value="ClaimResponse"/>
      <display value="ClaimResponse"/>
      <definition value="This resource provides the adjudication details from the processing of a Claim resource."/>
    </concept>
    <concept>
      <code value="ClinicalImpression"/>
      <display value="ClinicalImpression"/>
      <definition value="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 &quot;ClinicalI
      mpression&quot; rather than &quot;ClinicalAssessment&quot; to avoid confusion with the
       recording of assessment tools such as Apgar score."/>
    </concept>
    <concept>
      <code value="Communication"/>
      <display value="Communication"/>
      <definition value="An occurrence of information being transmitted; e.g. an alert that was sent to a responsible
       provider, a public health agency was notified about a reportable condition."/>
    </concept>
    <concept>
      <code value="CommunicationRequest"/>
      <display value="CommunicationRequest"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Composition"/>
      <display value="Composition"/>
      <definition value="A set of healthcare-related information that is assembled together into a single logical
       document 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. While a
       Composition defines the structure, it does not actually contain the content: rather the
       full content of a document is contained in a Bundle, of which the Composition is the first
       resource contained."/>
    </concept>
    <concept>
      <code value="ConceptMap"/>
      <display value="ConceptMap"/>
      <definition value="A statement of relationships from one set of concepts to one or more other concepts -
       either code systems or data elements, or classes in class models."/>
    </concept>
    <concept>
      <code value="Condition"/>
      <display value="Condition"/>
      <definition value="Use to record detailed information about conditions, problems or diagnoses recognized
       by a clinician. There are many uses including: recording a diagnosis during an encounter;
       populating a problem list or a summary statement, such as a discharge summary."/>
    </concept>
    <concept>
      <code value="Conformance"/>
      <display value="Conformance"/>
      <definition value="A conformance statement is a set of capabilities of a FHIR Server that may be used as
       a statement of actual server functionality or a statement of required or desired server
       implementation."/>
    </concept>
    <concept>
      <code value="Contract"/>
      <display value="Contract"/>
      <definition value="A formal agreement between parties regarding the conduct of business, exchange of information
       or other matters."/>
    </concept>
    <concept>
      <code value="Coverage"/>
      <display value="Coverage"/>
      <definition value="Financial instrument which may be used to pay for or reimburse health care products and
       services."/>
    </concept>
    <concept>
      <code value="DataElement"/>
      <display value="DataElement"/>
      <definition value="The formal description of a single piece of information that can be gathered and reported."/>
    </concept>
    <concept>
      <code value="DetectedIssue"/>
      <display value="DetectedIssue"/>
      <definition value="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, etc."/>
    </concept>
    <concept>
      <code value="Device"/>
      <display value="Device"/>
      <definition value="This resource identifies an instance of a manufactured item that is used in the provision
       of healthcare without being substantially changed through that activity. The device may
       be a medical or non-medical device.  Medical devices includes durable (reusable) medical
       equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment,
       and research for healthcare and public health.  Non-medical devices may include items
       such as a machine, cellphone, computer, application, etc."/>
    </concept>
    <concept>
      <code value="DeviceComponent"/>
      <display value="DeviceComponent"/>
      <definition value="Describes the characteristics, operational status and capabilities of a medical-related
       component of a medical device."/>
    </concept>
    <concept>
      <code value="DeviceMetric"/>
      <display value="DeviceMetric"/>
      <definition value="Describes a measurement, calculation or setting capability of a medical device."/>
    </concept>
    <concept>
      <code value="DeviceUseRequest"/>
      <display value="DeviceUseRequest"/>
      <definition value="Represents a request for a patient to employ a medical device. The device may be an implantable
       device, or an external assistive device, such as a walker."/>
    </concept>
    <concept>
      <code value="DeviceUseStatement"/>
      <display value="DeviceUseStatement"/>
      <definition value="A record of a device being used by a patient where the record is the result of a report
       from the patient or another clinician."/>
    </concept>
    <concept>
      <code value="DiagnosticOrder"/>
      <display value="DiagnosticOrder"/>
      <definition value="A record of a request for a diagnostic investigation service to be performed."/>
    </concept>
    <concept>
      <code value="DiagnosticReport"/>
      <display value="DiagnosticReport"/>
      <definition value="The findings and interpretation of diagnostic  tests performed on patients, groups of
       patients, devices, and locations, and/or specimens derived from these. The report includes
       clinical context such as requesting and provider information, and some mix of atomic results,
       images, textual and coded interpretations, and formatted representation of diagnostic
       reports."/>
    </concept>
    <concept>
      <code value="DocumentManifest"/>
      <display value="DocumentManifest"/>
      <definition value="A manifest that defines a set of documents."/>
    </concept>
    <concept>
      <code value="DocumentReference"/>
      <display value="DocumentReference"/>
      <definition value="A reference to a document ."/>
    </concept>
    <concept>
      <code value="DomainResource"/>
      <display value="DomainResource"/>
      <definition value="--- Abstract Type! ---A resource that includes narrative, extensions, and contained resources."/>
    </concept>
    <concept>
      <code value="EligibilityRequest"/>
      <display value="EligibilityRequest"/>
      <definition value="This resource provides the insurance eligibility details from the insurer regarding a
       specified coverage and optionally some class of service."/>
    </concept>
    <concept>
      <code value="EligibilityResponse"/>
      <display value="EligibilityResponse"/>
      <definition value="This resource provides eligibility and plan details from the processing of an Eligibility
       resource."/>
    </concept>
    <concept>
      <code value="Encounter"/>
      <display value="Encounter"/>
      <definition value="An interaction between a patient and healthcare provider(s) for the purpose of providing
       healthcare service(s) or assessing the health status of a patient."/>
    </concept>
    <concept>
      <code value="EnrollmentRequest"/>
      <display value="EnrollmentRequest"/>
      <definition value="This resource provides the insurance enrollment details to the insurer regarding a specified
       coverage."/>
    </concept>
    <concept>
      <code value="EnrollmentResponse"/>
      <display value="EnrollmentResponse"/>
      <definition value="This resource provides enrollment and plan details from the processing of an Enrollment
       resource."/>
    </concept>
    <concept>
      <code value="EpisodeOfCare"/>
      <display value="EpisodeOfCare"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="ExplanationOfBenefit"/>
      <display value="ExplanationOfBenefit"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="FamilyMemberHistory"/>
      <display value="FamilyMemberHistory"/>
      <definition value="Significant health events and conditions for a person related to the patient relevant
       in the context of care for the patient."/>
    </concept>
    <concept>
      <code value="Flag"/>
      <display value="Flag"/>
      <definition value="Prospective warnings of potential issues when providing care to the patient."/>
    </concept>
    <concept>
      <code value="Goal"/>
      <display value="Goal"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Group"/>
      <display value="Group"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="HealthcareService"/>
      <display value="HealthcareService"/>
      <definition value="The details of a healthcare service available at a location."/>
    </concept>
    <concept>
      <code value="ImagingObjectSelection"/>
      <display value="ImagingObjectSelection"/>
      <definition value="A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances).  The referenced
       SOP Instances (images or other content) are for a single patient, and may be from one
       or more studies. The referenced SOP Instances have been selected for a purpose, such as
       quality assurance, conference, or consult. Reflecting that range of purposes, typical
       ImagingObjectSelection resources may include all SOP Instances in a study (perhaps for
       sharing through a Health Information Exchange); key images from multiple studies (for
       reference by a referring or treating physician); a multi-frame ultrasound instance (&quot;cine&quot;
       video clip) and a set of measurements taken from that instance (for inclusion in a teaching
       file); and so on."/>
    </concept>
    <concept>
      <code value="ImagingStudy"/>
      <display value="ImagingStudy"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Immunization"/>
      <display value="Immunization"/>
      <definition value="Describes the event of a patient being administered a vaccination or a record of a vaccination
       as reported by a patient, a clinician or another party and may include vaccine reaction
       information and what vaccination protocol was followed."/>
    </concept>
    <concept>
      <code value="ImmunizationRecommendation"/>
      <display value="ImmunizationRecommendation"/>
      <definition value="A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's
       immunization eligibility according to a published schedule) with optional supporting justification."/>
    </concept>
    <concept>
      <code value="ImplementationGuide"/>
      <display value="ImplementationGuide"/>
      <definition value="A set of rules or how FHIR is used to solve a particular problem. 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."/>
    </concept>
    <concept>
      <code value="List"/>
      <display value="List"/>
      <definition value="A set of information summarized from a list of other resources."/>
    </concept>
    <concept>
      <code value="Location"/>
      <display value="Location"/>
      <definition value="Details and position information for a physical place where services are provided  and
       resources and participants may be stored, found, contained or accommodated."/>
    </concept>
    <concept>
      <code value="Media"/>
      <display value="Media"/>
      <definition value="A photo, video, or audio recording acquired or used in healthcare. The actual content
       may be inline or provided by direct reference."/>
    </concept>
    <concept>
      <code value="Medication"/>
      <display value="Medication"/>
      <definition value="This resource is primarily used for the identification and definition of a medication.
       It covers the ingredients and the packaging for a medication."/>
    </concept>
    <concept>
      <code value="MedicationAdministration"/>
      <display value="MedicationAdministration"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="MedicationDispense"/>
      <display value="MedicationDispense"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="MedicationOrder"/>
      <display value="MedicationOrder"/>
      <definition value="An order for both supply of the medication and the instructions for administration of
       the medication to a patient. The resource is called &quot;MedicationOrder&quot; rather
       than &quot;MedicationPrescription&quot; to generalize the use across inpatient and outpatient
       settings as well as for care plans, etc."/>
    </concept>
    <concept>
      <code value="MedicationStatement"/>
      <display value="MedicationStatement"/>
      <definition value="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 e.g. 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 medication statement and a
       medication administration is that the medication administration has complete administration
       information and is based on actual administration information from the person who administered
       the medication.  A medication statement 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."/>
    </concept>
    <concept>
      <code value="MessageHeader"/>
      <display value="MessageHeader"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="NamingSystem"/>
      <display value="NamingSystem"/>
      <definition value="A curated namespace that issues unique symbols within that namespace for the identification
       of concepts, people, devices, etc.  Represents a &quot;System&quot; used within the Identifier
       and Coding data types."/>
    </concept>
    <concept>
      <code value="NutritionOrder"/>
      <display value="NutritionOrder"/>
      <definition value="A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to
       a patient/resident."/>
    </concept>
    <concept>
      <code value="Observation"/>
      <display value="Observation"/>
      <definition value="Measurements and simple assertions made about a patient, device or other subject."/>
    </concept>
    <concept>
      <code value="OperationDefinition"/>
      <display value="OperationDefinition"/>
      <definition value="A formal computable definition of an operation (on the RESTful interface) or a named query
       (using the search interaction)."/>
    </concept>
    <concept>
      <code value="OperationOutcome"/>
      <display value="OperationOutcome"/>
      <definition value="A collection of error, warning or information messages that result from a system action."/>
    </concept>
    <concept>
      <code value="Order"/>
      <display value="Order"/>
      <definition value="A request to perform an action."/>
    </concept>
    <concept>
      <code value="OrderResponse"/>
      <display value="OrderResponse"/>
      <definition value="A response to an order."/>
    </concept>
    <concept>
      <code value="Organization"/>
      <display value="Organization"/>
      <definition value="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, etc."/>
    </concept>
    <concept>
      <code value="Parameters"/>
      <display value="Parameters"/>
      <definition value="This special resource type is used to represent an operation request and response (operations.html).
       It has no other use, and there is no RESTful endpoint associated with it."/>
    </concept>
    <concept>
      <code value="Patient"/>
      <display value="Patient"/>
      <definition value="Demographics and other administrative information about an individual or animal receiving
       care or other health-related services."/>
    </concept>
    <concept>
      <code value="PaymentNotice"/>
      <display value="PaymentNotice"/>
      <definition value="This resource provides the status of the payment for goods and services rendered, and
       the request and response resource references."/>
    </concept>
    <concept>
      <code value="PaymentReconciliation"/>
      <display value="PaymentReconciliation"/>
      <definition value="This resource provides payment details and claim references supporting a bulk payment."/>
    </concept>
    <concept>
      <code value="Person"/>
      <display value="Person"/>
      <definition value="Demographics and administrative information about a person independent of a specific health-related
       context."/>
    </concept>
    <concept>
      <code value="Practitioner"/>
      <display value="Practitioner"/>
      <definition value="A person who is directly or indirectly involved in the provisioning of healthcare."/>
    </concept>
    <concept>
      <code value="Procedure"/>
      <display value="Procedure"/>
      <definition value="An action that is or was performed on a patient. This can be a physical intervention like
       an operation, or less invasive like counseling or hypnotherapy."/>
    </concept>
    <concept>
      <code value="ProcedureRequest"/>
      <display value="ProcedureRequest"/>
      <definition value="A request for a procedure to be performed. May be a proposal or an order."/>
    </concept>
    <concept>
      <code value="ProcessRequest"/>
      <display value="ProcessRequest"/>
      <definition value="This resource provides the target, request and response, and action details for an action
       to be performed by the target on or about existing resources."/>
    </concept>
    <concept>
      <code value="ProcessResponse"/>
      <display value="ProcessResponse"/>
      <definition value="This resource provides processing status, errors and notes from the processing of a resource."/>
    </concept>
    <concept>
      <code value="Provenance"/>
      <display value="Provenance"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Questionnaire"/>
      <display value="Questionnaire"/>
      <definition value="A structured set of questions intended to guide the collection of answers. The questions
       are ordered and grouped into coherent subsets, corresponding to the structure of the grouping
       of the underlying questions."/>
    </concept>
    <concept>
      <code value="QuestionnaireResponse"/>
      <display value="QuestionnaireResponse"/>
      <definition value="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 underlying
       questions."/>
    </concept>
    <concept>
      <code value="ReferralRequest"/>
      <display value="ReferralRequest"/>
      <definition value="Used to record and send details about a request for referral service or transfer of a
       patient to the care of another provider or provider organization."/>
    </concept>
    <concept>
      <code value="RelatedPerson"/>
      <display value="RelatedPerson"/>
      <definition value="Information about a person that is involved in the care for a patient, but who is not
       the target of healthcare, nor has a formal responsibility in the care process."/>
    </concept>
    <concept>
      <code value="Resource"/>
      <display value="Resource"/>
      <definition value="--- Abstract Type! ---This is the base resource type for everything."/>
    </concept>
    <concept>
      <code value="RiskAssessment"/>
      <display value="RiskAssessment"/>
      <definition value="An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood
       of each outcome."/>
    </concept>
    <concept>
      <code value="Schedule"/>
      <display value="Schedule"/>
      <definition value="A container for slot(s) of time that may be available for booking appointments."/>
    </concept>
    <concept>
      <code value="SearchParameter"/>
      <display value="SearchParameter"/>
      <definition value="A search parameter that defines a named search item that can be used to search/filter
       on a resource."/>
    </concept>
    <concept>
      <code value="Slot"/>
      <display value="Slot"/>
      <definition value="A slot of time on a schedule that may be available for booking appointments."/>
    </concept>
    <concept>
      <code value="Specimen"/>
      <display value="Specimen"/>
      <definition value="A sample to be used for analysis."/>
    </concept>
    <concept>
      <code value="StructureDefinition"/>
      <display value="StructureDefinition"/>
      <definition value="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."/>
    </concept>
    <concept>
      <code value="Subscription"/>
      <display value="Subscription"/>
      <definition value="The subscription resource is used to define a push based subscription from a server to
       another system. Once a subscription is registered with the server, the server checks every
       resource that is created or updated, and if the resource matches the given criteria, it
       sends a message on the defined &quot;channel&quot; so that another system is able to take
       an appropriate action."/>
    </concept>
    <concept>
      <code value="Substance"/>
      <display value="Substance"/>
      <definition value="A homogeneous material with a definite composition."/>
    </concept>
    <concept>
      <code value="SupplyDelivery"/>
      <display value="SupplyDelivery"/>
      <definition value="Record of delivery of what is supplied."/>
    </concept>
    <concept>
      <code value="SupplyRequest"/>
      <display value="SupplyRequest"/>
      <definition value="A record of a request for a medication, substance or device used in the healthcare setting."/>
    </concept>
    <concept>
      <code value="TestScript"/>
      <display value="TestScript"/>
      <definition value="TestScript is a resource that specifies a suite of tests against a FHIR server implementation
       to determine compliance against the FHIR specification."/>
    </concept>
    <concept>
      <code value="ValueSet"/>
      <display value="ValueSet"/>
      <definition value="A value set specifies a set of codes drawn from one or more code systems."/>
    </concept>
    <concept>
      <code value="VisionPrescription"/>
      <display value="VisionPrescription"/>
      <definition value="An authorization for the supply of glasses and/or contact lenses to a patient."/>
    </concept>
  </codeSystem>
</ValueSet>