FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

4.4.1.412 ValueSet http://hl7.org/fhir/ValueSet/event-resource-types

FHIR Infrastructure icon Work Group Maturity Level: NNormative Use Context: Country: World
Official URL: http://hl7.org/fhir/ValueSet/event-resource-types Version: 6.0.0-cibuild
active as of 2024-07-19 Computable Name: EventResourceTypes
Flags: Immutable OID: 2.16.840.1.113883.4.642.3.1060

This value set is not currently used

All Resource Types that represent event resources


  • Include these codes as defined in http://hl7.org/fhir/fhir-types
    CodeDisplayDefinition
    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.
    AuditEventAuditEventA record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis.
    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.
    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.
    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.
    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.).
    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.
    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.
    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.
    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).
    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.
    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.
    GenomicStudyGenomicStudyA set of analyses performed to analyze and generate genomic data.
    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.
    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 from a DICOM SR Content Item or a Segment Number from a DICOM Segmentation SOP Instance.
    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.
    InventoryReportInventoryReportA report of inventory or stock items.
    InvoiceInvoiceInvoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.
    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.
    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.
    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.
    NutritionIntakeNutritionIntakeA record of intake by a patient. A NutritionIntake may indicate that the patient may be consuming the food or fluid now or has consumed the food (i.e. solid and/or liquid), breastmilk, infant formula, supplements, enteral formula now or has consumed it 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.
    ObservationObservationMeasurements and simple assertions made about a patient, device or other subject.
    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.
    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.
    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.
    RiskAssessmentRiskAssessmentAn assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome.
    SupplyDeliverySupplyDeliveryRecord of delivery of what is supplied.
    TransportTransportRecord of transport.

 

This expansion generated 19 Jul 2024


Expansion based on codesystem All FHIR Types v6.0.0-cibuild (CodeSystem)

This value set contains 43 concepts.

CodeSystemDisplayDefinition
  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.

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

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

  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.

  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.

  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.

  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.).

  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.

  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.

  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.

  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).

  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.

  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.

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

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

  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.

  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 from a DICOM SR Content Item or a Segment Number from a DICOM Segmentation SOP Instance.

  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.

  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.

  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.

  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.

  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.

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

A record of intake by a patient. A NutritionIntake may indicate that the patient may be consuming the food or fluid now or has consumed the food (i.e. solid and/or liquid), breastmilk, infant formula, supplements, enteral formula now or has consumed it 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.

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

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

  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.

  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.

  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.

  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.

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

Record of delivery of what is supplied.

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

Record of transport.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code