Oracle Health Real-World Data Core Model

Describes the main data types and structures in the Oracle Health Real-World Data Core Model and what information they contain.

Core Model Domains

Real-World Data is deidentified with the Safe Harbor method for Provider and Academic clients, and with the Expert Determination method for life sciences customer projects. See Real-World Data Expert Determination Data Dictionary for downloadable data dictionaries.

The following diagram displays the structure of data in the Real-World Data Core Model:

Domain	Description
Demographics	Demographics data describes the demographic information for a patient such as gender, race, ethnicity, and marital status.
Encounter	Encounter information represents a planned, current, or past interaction between the patient and one or more health care providers. For example, an encounter can represent an inpatient hospitalization, an ambulatory or outpatient visit, an emergency department visit, a home health visit at the patient’s residence, or a virtual encounter through email or teleconference.
Allergy	The person's allergies, which indicate a susceptibility to an adverse reaction upon exposure to a specified allergen. An allergen can be a food substance, an environmental substance, a biologic substance, a medication substance, a pharmaceutical product, or a class of substances (such as penicillins). Negation of an allergen can be holistic (No Known Allergies), per category (No Known Drug Allergies), or per substance (No Known Latex Allergy). Allergies result in an undesirable physiologic reaction to an amount of a substance that would not produce a reaction in most individuals. The allergy list represents a propensity unique to this individual for a reaction upon future exposure to a specified substance. It excludes clinically identical episodes that may be caused by physical agents, for example, cold, sunlight, vibration, exercise activity, or infectious agents.
Clinical Event	Derived from the Result table, clinical event data contains clinical event results for a person, including tobacco use, visit type, observations of disease, conditions, and symptoms.
Condition	Condition information describes the health state of the person including diagnoses and problems. Diagnoses are typically captured in the context of a specific encounter or visit for the purpose of billing. Problems can be anything that has risen to the level of concern or warrants management or tracking through a problem list. Conditions are not limited to diseases and illnesses and can be acute or chronic.
Immunization	Immunization information contains the vaccines that have been administered to the person and documentation of administrations that were refused, contraindicated, or not given.
Lab	Derived from the Result table, lab data contains laboratory results for a person, including specimen collection and fluid, respiratory, tissue, and other samples.
Measurement	Derived from the Result table, the measurement data contains measurement results for a person, including temperature, heart rate, BMI, and blood pressure.
Medication	Medication information describes all medications prescribed for the person or consumed by the person including inpatient and outpatient pharmacy orders, retail pharmacy prescriptions, over-the-counter medications, and dietary supplements.
Medication Administration	Medication administration events describe a person consuming or being administered a medication, for example swallowing a tablet or a long-running infusion.
Order List	Order list information is a list of the person's orders created on a given date by a specified provider and can include the order reconciliation actions that a provider determines upon discharge or the person's compliance status per order. When the order list is empty, the Order List Model supports documentation of an empty reason for situations where compliance was unable to be obtained due to the person being unconscious or reconciliation is not applicable because the person has no known medications.
Problem List	A list extracted from the Condition model where condition data with this problem type (with the coding system IDs of type.standard.id = 55607006 and type.standard.codingSystemId = 2.16.840.1.113883.6.96) are removed from the condition model and added to the Problem List table.
Procedure	Procedure information describes procedures performed on a person. This can be physical (an operation) or less invasive (counseling or hypnotherapy).
Provider Demographics	Provider demographics data describes the provider ID, CMS classification, CMS specialization, and tenant.
Preferred Demographics	Based on the Demographics table, the Preferred Demographics table contains demographic information in a single record and as a distinct value. This table is intended to resolve conflicts when you have multiple discrepant entries from an array, multiple rows per patient, and an invalid or uninterpretable (non-meaningful) entries. Oracle determines the most appropriate or preferred value for a patient.
Questionnaire	Questionnaire data describes a structured set of questions and their responses about the person. Questionnaires cover the need to communicate data originating from forms, for example, Social History or Outcome and Assessment Information Set (OASIS) assessments.
Tenant Attributes	An additional metadata output table that is provided to help describe the tenants contributing to Real-World Data.