FHIR Relational Schema Data Dictionary

allergy_intolerance

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

allergy_intolerance_code

This table holds the primary keys of all unique AllergyIntolerance code groups. A code group captures the set of codes representing a particular allergy or intolerance. Individual codings within each group are in the allergy_intolerance_code_coding table.

allergy_intolerance_code_coding

This table contains individual coding values for each AllergyIntolerance code group.

allergy_intolerance_identifier

This is a bridge table that joins the allergy_intolerance table to the identifier table.

allergy_intolerance_note

This table contains freeform text notes with extra information about the AllergyIntolerance that is not captured in other attributes.

allergy_intolerance_reaction

Details about each adverse reaction event linked to exposure to the identified substance.

allergy_intolerance_reaction_manifestation

This table captures concept groups thta represent the clinical symptoms and/or signs that are observed or associated with the adverse reaction event. Individual codings within each group are in the allergy_intolerance_reaction_manifestation_coding table.

allergy_intolerance_reaction_manifestation_coding

This table contains individual coding values for each reaction manifestation group.

appointment

A FHIR Appointment represents 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).

appointment_identifier

This is a bridge table that joins the appointment table to the identifier table

appointment_participant_location

This table contains a list of locations involved in each appointment. These entries come from the Appointment.participant array in the FHIR resource, filtered down to the entries that are locations.

appointment_participant_practitioner

This table contains a list of practitioners involved in each appointment. These entries come from the Appointment.participant array in the FHIR resource, filtered down to the entries that are practitioners.

appointment_participant_practitioner_type

This table contains the primary keys of all unique concepts representing roles of practitioners involved in an appoinment. Individual codings within each group are in the appointment_participant_practitioner_type_coding table,

appointment_participant_practitioner_type_coding

This relation contains the individual coding values for each practitioner type

appointment_type

This table contains the primary keys of all unique concept groups that represnet the style of appointment or patient that has been booked in the slot. This is distinct from the service type. Individual codings within each group are in the appointment_type_coding table.

appointment_type_coding

This relation contains the individual coding values for each appointment type.

care_plan

A FHIR CarePlan 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.

care_plan_activity

Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etc.

care_plan_activity_code

The activity code represents a detailed description of the type of planned activity; e.g. what lab test, what procedure, what kind of encounter. This table comtains the primary keys of all unique activity codes. Individual codings within each group are in the care_plan_activity_code_coding table.

care_plan_activity_code_coding

This relation contains the individual coding values for each CarePlan activity code. These are codes for different types of procedures.

care_plan_activity_product

Care plan activity products identify the food, drug or other product to be consumed or supplied in the activity. This table contains the primary keys of all unique activity products. Individual codings within each group are in the care_plan_activity_product_coding table.

care_plan_activity_product_coding

This relation contains the individual coding values for each product administered/supplied for the CarePlan activity. These are most commonly RxNorm codes.

care_plan_goal

This table contains references to the goal resources that represent the goals that the care plan is intended to contribute towards meeting

care_plan_identifier

This is a bridge table that joins the care_plan table to the identifier table

care_plan_note

This table contains freeform text notes with extra information about the CarePlan that is not captured in other attributes

care_team

A FHIR CareTeam includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.

care_team_identifier

This is a bridge table that joins the care_team table to the identifier table

care_team_participant

Identifies all people and organizations who are expected to be involved in the care team.

care_team_participant_role

The care team participant role indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc. This table contains the primary keys of all unique concepts representing roles of care team participant roles. Individual codings within each group are in the care_team_participant_role_coding table.

care_team_participant_role_coding

This relation contains the individual coding values for each care team participant role.

care_team_telecom

This is a bridge table between care teams and contact details. These represent central contact details for the care team (that applies to all members).

condition

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

condition_category

The condition category describes whether a condition comes from a problem list or was diagnosed in a specific context. This table contains the primary keys of all unique concept groups that represent the condition categories. Individual codings within each group are in the condition_category_coding table.

condition_category_coding

This relation contains the individual coding values for each condition category.

condition_code

The condition code represents a detailed description of the type of condition; e.g. what this, what diagnosis, what kind of problem. This table contains the primary keys of all unique concepts representing condition codes. Individual codings within each group are in the condition_code_coding table.

condition_code_coding

This relation contains the individual coding values for each condition code.

condition_identifier

This is a bridge table that joins the condition table to the identifier table

condition_note

This table contains freeform text notes with extra information about the Condition that is not captured in other attributes

consent

A FHIR Consent is a record of a healthcare consumer's choices, 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.

consent_category

The consent category classfies the type of consents foundd in the statement, such as Advance Directive, Do Not Resuscitate, etc. This table contains the primary keys of all unique concept groups that represent the consent categories. Individual codings within each group are in the consent_category_coding table.

consent_category_coding

This relation contains the individual coding values for each consent category.

consent_identifier

This is a bridge table that joins the consent table to the identifier table

consent_policy_rule

The consent policy rule represents specific base computable regulation or policy. This table contains the primary keys of all unique concept groups that represent the consent policy rules. Individual codings within each group are in the consent_policy_rule_coding table.

consent_policy_rule_coding

This relation contains the individual coding values for each consent policy rule.

consent_provision_actor

The consent provision actor describes who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').

consent_provision_actor_role

The consent provision actor role describes ow the individual is involved in the consent provision. This table contains the primary keys of all unique concept groups that represent the consent provision actor roles. Individual codings within each group are in the consent_provision_actor_role_coding table.

consent_provision_actor_role_coding

This relation contains the individual coding values for each consent provision actor role.

coverage

A FHIR Coverage represents a financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.

coverage_identifier

This is a bridge table that joins the coverage table to the identifier table

coverage_payor

Issuer of the policy

coverage_type

The type of coverage may be a social program, medical plan, accident coverage (workers compensation, auto), group health or payment by an individual or organization. This table contains the primary keys of all unique concept groups that represent the coverage types. Individual codings within each group are in the coverage_type_coding table.

coverage_type_coding

This relation contains the individual coding values for each coverage type.

device

Item used in healthcare.

device_identifier

This is a bridge table that joins the device table to the identifier table

device_name

This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.

device_note

This table contains freeform text notes with extra information about the Device that is not captured in other attributes

device_specialization_system_type_bridge

The device specialization system type expresses the standard that is used to operate and communicate the device. This is a bridge table that joins Device resources to device specialization system type codeable concepts. Individual codings within each group are in the

device_specialization_system_type_coding

This relation contains the individual coding values for each device specialization system type.

device_udi_carrier

Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.

device_use_statement

A FHIR DeviceUseStatement represents 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.

device_use_statement_derived_from

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

device_use_statement_identifier

This is a bridge table that joins the device_use_statement table to the identifier table

diagnostic_report

A FHIR DiagnosticReport represents the findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these.

diagnostic_report_code

The diagnostic report code represents the name or code for the diagnostic report. This table contains the primary keys of all unique concept groups that represent the diagnostic report codes. Individual codings within each group are in the diagnostic_report_code_coding table.

diagnostic_report_code_coding

This relation contains the individual coding values for each diagnostic report code.

diagnostic_report_identifier

This is a bridge table that joins the diagnostic_report table to the identifier table

diagnostic_report_performer

The diagnostic report performer represents the diagnostic service that is responsible for issuing the report.

diagnostic_report_result

This table contains references to Observation resources that are part of this diagnostic report.

document_reference

A FHIR DocumentReference represents a reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text.

document_reference_category_bridge

The document reference category helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. This is a bridge table that joins DocumentReference resources to DocumentReference category codeable concepts. Individual codings within each group are in the document_reference_category_coding table.

document_reference_category_coding

This relation contains the individual coding values for each document reference category.

document_reference_identifier

This is a bridge table that joins the document_reference table to the identifier table

document_reference_relates_to

Relationships that this document has with other document references that already exist.

document_reference_type

Specifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. This table contains the primary keys of all unique concept groups that represent the document reference types. Individual codings within each group are in the document_reference_type_coding table.

document_reference_type_coding

This relation contains the individual coding values for each document reference type.

encounter

A FHIR Encounter represents 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.

encounter_diagnosis

The list of diagnosis relevant to Encounters

encounter_hospitalization_discharge_disposition

The discharge disposition represents the category or kind of location after discharge. This table contains the primary keys of all unique concept groups that represent the discharge dispositions. Individual codings within each group are in the encounter_hospitalization_discharge_disposition_coding table.

encounter_hospitalization_discharge_disposition_coding

This relation contains the individual coding values for each encounter hospitalization discharge disposition.

encounter_identifier

This is a bridge table that joins the encounter table to the identifier table

encounter_participant

An Encounter Participant represents the list of people involved in the Encounter.

encounter_participant_type

The encounter participant type represents the role of the participant in the encounter. This table contains the primary keys of all unique concept groups that represent the encounter participant types. Individual codings within each group are in the encounter_participant_type_coding table.

encounter_participant_type_coding

This relation contains the individual coding values for each encounter participant type.

encounter_reason_code

The encounter reason code encodes the reason the encounter takes place. For admissions, this can be used for a coded admission diagnosis. This table contains the primary keys of all unique concept groups that represent the encounter reason codes. This table contains the extracted SNOMED, ICD-10-CM, and ICD-9-CM codes of the encounter reason.

encounter_type

The encounter type specifies the type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). This table contains the primary keys of all unique concept groups that represent the encounter types. Individual codings within each group are in the encounter_type_coding table.

encounter_type_coding

This relation contains the individual coding values for each encounter type.

family_member_history

Information about patients relatives, relevant for patient.

family_member_history_condition

This table contains a list of significant Conditions (or condition) that the family member had.

family_member_history_condition_code

The family member history condition code encodes the actual condition that the family member had. This table contains the primary keys of all unique concept groups that represent the family member history condition codes. Individual codings within each group are in the family_member_history_condition_code_coding table.

family_member_history_condition_code_coding

This relation contains the individual coding values for each family member history condition code.

family_member_history_identifier

This is a bridge table that joins the family_member_history table to the identifier table

family_member_history_note

This table contains freeform text notes with extra information about the FamilyMemberHistory that is not captured in other attributes

family_member_history_relationship

The family member history relationship code encodes thetype of relationship this person has to the patient (father, mother, brother etc.). This table contains the primary keys of all unique concept groups that represent the family member history relationship codes. Individual codings within each group are in the family_member_history_relationship_coding table.

family_member_history_relationship_coding

This relation contains the individual coding values for each family member history relationship.

goal

Describes the intended objective(s) for a patient, group or organization

goal_description

The goal description encodes a specific desired objective of care, such as "control blood pressure" or "negotiate an obstacle course" or "dance with child at wedding". This table contains the primary keys of all unique concept groups that represent the goal descriptions. Individual codings within each group are in the goal_description_coding table.

goal_description_coding

This relation contains the individual coding values for each goal description.

goal_identifier

This is a bridge table that joins the goal table to the identifier table

goal_target

The goal target indicates what should be done by when.

goal_target_measure

The target measure expresses the parameter whose value is being tracked, e.g. body weight, blood pressure, or hemoglobin A1c level. This table contains the primary keys of all unique concept groups that represent the goal target measures. Individual codings within each group are in the goal_target_measure_coding table.

goal_target_measure_coding

This relation contains the individual coding values for each goal target measure.

immunization

A FHIR Immunization represents 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.

immunization_identifier

This is a bridge table that joins the immunization table to the identifier table

immunization_note

This table contains freeform text notes with extra information about the Immunization that is not captured in other attributes

immunization_status_reason

The immunization status reason indicates the reason the immunization event was not performed. This table contains the primary keys of all unique concept groups that represent the immunization status reasons. Individual codings within each group are in the immunization_status_reason_coding table.

immunization_status_reason_coding

This relation contains the individual coding values for each immunization status reason.

immunization_vaccine_code

The immunization vaccine code encodes the vaccine that was administered or was to be administered. This table contains the primary keys of all unique concept groups that represent the immunization vaccine codes. Individual codings within each group are in the immunization_vaccine_code_coding table.

immunization_vaccine_code_coding

This relation contains the individual coding values for each immunization vaccine code.

lens_encounter

A summarized Encounter deduplicated by ActEncounter code

lens_encounter_aggregated_from

This relation joins Lens Encounter resources to Zus aggregatedFrom extensions. The Zus aggregated from extension lists the Encounter resources that were used to generate this output resource.

lens_encounter_diagnosis

The list of diagnosis relevant to Lens Encounters

lens_encounter_hospitalization_discharge_disposition

The discharge disposition represents the category or kind of location after discharge. This table contains the primary keys of all unique concept groups that represent the discharge dispositions. Individual codings within each group are in the encounter_hospitalization_discharge_disposition_coding table.

lens_encounter_hospitalization_discharge_disposition_coding

This relation contains the individual coding values for each encounter hospitalization discharge disposition.

lens_encounter_identifier

This is a bridge table that joins the lens encounter table to the identifier table

lens_encounter_participant

A Lens Encounter Participant represents the list of people involved in the Lens Encounter.

lens_encounter_related_binaries

Zus derives Lens Encounter resources from encounter resources sourced from CDA documents, which are stored in Zus as binary resources. This table lists the binary resource IDs from which a Lens Encounter resource was derived. The logic by which Lens Encounter resources are derived is described here https://docs.zushealth.com/docs/viewing-zus-data-with-a-lens#encounter-lens.

lens_encounter_type

The encounter type specifies the type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). This table contains the primary keys of all unique concept groups that represent the encounter types. Individual codings within each group are in the encounter_type_coding table.

lens_encounter_type_coding

This relation contains the individual coding values for each encounter type.

lens_rxnorm_medication_statement

A summarized MedicationStatement deduplicated by RxNorm code, aggregated from other medication statements, medication requests, dispenses, and administrations.

lens_snomed_condition

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

lens_snomed_condition_code

The condition code represents a detailed description of the type of condition; e.g. what this, what diagnosis, what kind of problem. This table contains the primary keys of all unique concepts representing condition codes. Individual codings within each group are in the lens_snomed_condition_code_coding table.

lens_snomed_condition_code_coding

This relation contains the individual coding values for each lens snomed condition code.

lens_transition_of_care

A FHIR LensTransitionOfCare describes the 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.

lens_transition_of_care_adt_message

ADT message details associated with each LensTransitionOfCare

lens_transition_of_care_aggregated_from

This relation joins LensTransitionOfCare resources to Zus aggregatedFrom extensions. The Zus aggregated from extension lists the Encounter resources that were used to generate this output resource.

lens_transition_of_care_diagnosis

The list of diagnosis relevant to this LensTransitionOfCare

lens_transition_of_care_discharge_disposition

This table represents the discharge disposition of the patient at the end of the transition of care. This table contains the primary keys of all unique concept groups that represent the discharge dispositions. Individual codings within each group are in the lens_transition_of_care_discharge_disposition_coding table.

lens_transition_of_care_discharge_disposition_coding

This relation contains the individual coding values for each lens transition of care discharge disposition.

lens_transition_of_care_identifier

This is a bridge table that joins the lens_transition_of_care table to the identifier table

location

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

location_identifier

This is a bridge table that joins the location table to the identifier table

location_physical_type

The location physical type represents the physical form of a location, e.g. building, room, vehicle, road. This table contains the primary keys of all unique concept groups that represent the location physical types. Individual codings within each group are in the location_physical_type_coding table.

location_physical_type_coding

This relation contains the individual coding values for each location physical type.

location_telecom

Contact details of the Location

location_type

The location type indicates the type of function performed at a location. This table contains the primary keys of all unique concept groups that represent the location types. Individual codings within each group are in the location_type_coding table.

location_type_coding

This relation contains the individual coding values for each location type.

medication

The FHIR Medication resource is used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.

medication_administration

FHIR MedicationAdministration 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.

medication_administration_identifier

This is a bridge table that joins the medication_administration table to the identifier table

medication_administration_reason_code

The reason code indicates why the medication was given. This table contains the extracted SNOMED codes of the medication administration reason codes.

medication_administration_reason_reference

Condition that supports why the medication was administered

medication_dispense

This resource covers the supply of medications to a patient. Examples include dispensing and pick-up from an outpatient or community pharmacy, dispensing patient-specific medications from inpatient pharmacy to ward, as well as issuing a single dose from ward stock to a patient for consumption. The medication dispense is the result of a pharmacy system responding to a medication order.

medication_dispense_identifier

This is a bridge table that joins the medication_dispense table to the identifier table

medication_form

The medication form describes the form of the medication, e.g. tablet, capsule, powder, etc. This table contains the primary keys of all unique concept groups that represent the medication forms. Individual codings within each group are in the medication_form_coding table.

medication_form_coding

This relation contains the individual coding values for each medication form.

medication_ingredient

The medication ingredient identifies a particular constituent of interest in the product.

medication_ingredient_item_code

The medicaiton ingredient item code represents the actual ingredient - either a substance (simple ingredient) or another medicationof a medication. This table contains the primary keys of all unique concept groups that represent the medication ingredient item codes. Individual codings within each group are in the medication_ingredient_item_code_coding table.

medication_ingredient_item_code_coding

This relation contains the individual coding values for each medication ingredient item code.

medication_request

A FHIR MedicationRequest resource represents nn order or request for both supply of the medication and the instructions for administration of the medication to a patient.

medication_request_category

The medication request category indicates the type of medication request (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)). This table contains the primary keys of all unique concept groups that represent the medication request categories. Individual codings within each group are in the medication_request_category_coding table.

medication_request_category_coding

This relation contains the individual coding values for each medication request category.

medication_request_identifier

This is a bridge table that joins the medication_request table to the identifier table

medication_request_note

This table contains freeform text notes with extra information about the MedicationRequest that is not captured in other attributes

medication_request_reason_code_bridge

The medication request reason code encodes the reason for ordering or not ordering a medication. This is a bridge table that joins MedicationRequest resources to the reason code concept. Individual codings within each group are in the medication_request_reason_code_coding table.

medication_request_reason_reference

This relation joins MedicationRequest to the Condition that supports why the prescription is being written.

medication_request_reason_code_coding

This relation contains the individual coding values for each medication request reason code.

medication_statement

A FHIR MedicationStatement represents 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

medication_statement_dosage

This is a bridge table that joins the medication_statement table to the dosage table.

medication_statement_identifier

This is a bridge table that joins the medication_statement table to the identifier table

medication_statement_note

This table contains freeform text notes with extra information about the MedicationStatement that is not captured in other attributes

medication_statement_reason_code_bridge

The medication statement reason code encodes the reason for why the medication is being or was taken. This is a bridge table that joins MedicationStatement resources to the reason code concepts. Individual codings within each group are in the medication_statement_reason_code_coding table.

medication_statement_reason_code_coding

This relation contains the individual coding values for each medication statement reason code.

observation

A FHIR Observation represents measurements and simple assertions made about a patient, device or other subject.

observation_code

The observation code describes what was observed. Seomtimes this is called the observation "name". THis table contains the primary keys of all unique concept groups that represent the observation codes. Individual codings within each group are in the observation_code_coding table.

observation_code_coding

This relation contains the individual coding values for each observation code.

observation_identifier

This is a bridge table that joins the observation table to the identifier table

observation_interpretation

The observation interpretation is a categorical assessment of an observation value. For example, high, low, normal. This table contains the primary keys of all unique concept groups that represent the observation interpretations. Individual codings within each group are in the observation_interpretation_coding table.

observation_interpretation_coding

This relation contains the individual coding values for each observation interpretation.

observation_method

The observation method indicates the mechanism used to perform the observation. This table contains the primary keys of all unique concept groups that represent the observation methods. Individual codings within each group are in the observation_method_coding table.

observation_method_coding

This relation contains the individual coding values for each observation method.

observation_note

This table contains freeform text notes with extra information about the Observation that is not captured in other attributes

observation_performer

Who is responsible for the observation. Each Observation may have multiple categories. This relation joins Observations to the reference that encode the performers for the observation.

observation_value_concept

The observation value, encoded as a codeable concept. This table contains the primary keys of all unique concept groups that represent the observation value concepts. Individual codings within each group are in the observation_value_concept_coding table.

observation_value_concept_coding

This relation contains the individual coding values for each observation value concept.

organization

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

organization_identifier

This is a bridge table that joins the organization table to the identifier table

organization_telecom

Contact detail for the organization

organization_type

The kind of organization that this resource represents. This table contains the primary keys of all unique concept groups that represent the organization types. Individual codings within each group are in the organization_type_coding table.

organization_type_coding

This relation contains the individual coding values for each organization type.

patient

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

patient_address

This relation joins patients to their addresses

patient_communication

A language which may be used to communicate with the patient about his or her health

patient_communication_language

The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. This table contains the primary keys of all unique concept groups that represent the patient communication languages. Individual codings within each group are in the patient_communication_language_coding table.

patient_communication_language_coding

This relation contains the individual coding values for each patient communication language.

patient_contact

A contact party (e.g. guardian, partner, friend) for the patient

patient_contact_telecom

This relation joins patient contacts to the contact details

patient_general_practitioner

This table includes a list of nominated care providers for the patient.

patient_identifier

This is a bridge table that joins the patient table to the identifier table

patient_name

This is a bridge table that joins the patient table to the human name table.

patient_telecom

This relation joins patients to their contact details

practitioner

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

practitioner_identifier

This is a bridge table that joins the practitioner table to the identifier table

practitioner_qualification

Certification, licenses, or training pertaining to the provision of care

practitioner_qualification_coding

Representation of a defined practitioner qualification concept using a symbol from a defined terminology system

practitioner_telecom

A contact detail for the practitioner (that apply to all roles)

procedure

A FHIR Procedure represents an action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.

procedure_code

The procedure code expresses the specific Procedure that is performed. This table contains the primary keys of all unique concept groups that represent the procedure codes. Individual codings within each group are in the procedure_code_coding table.

procedure_code_coding

This relation contains the individual coding values for each procedure code.

procedure_identifier

This is a bridge table that joins the procedure table to the identifier table

procedure_note

This table contains freeform text notes with extra information about the Procedure that is not captured in other attributes

related_person

A FHIR RelatedPerson represents 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

related_person_identifier

This is a bridge table that joins the related_person table to the identifier table

related_person_relationship

The nature of the relationship between a patient and the related person. This table contains the primary keys of all unique concept groups that represent the related person relationships. Individual codings within each group are in the related_person_relationship_coding table.

related_person_relationship_coding

This relation contains the individual coding values for each related person relationship.

related_person_telecom

A contact detail for the person, e.g. a telephone number or an email address.

body_site_concept

Representation of the body site where a procedure, immunization, etc. took place

body_site_concept_coding

Representation of a defined body site concept using a symbol from a defined terminology system

contact_point

Details for all kinds of technology-mediated contact points for a person or organization, including telephone, email, etc.

dosage

Instructions for how a medication should be taken.

dosage_method

The dosage method expresses the technique for administering medication. This table contains the primary keys of all unique concept groups that represent the dosage methods. Individual codings within each group are in the dosage_method_coding table.

dosage_method_coding

Representation of a defined dosage method concept using a symbol from a defined terminology system

human_name

A name of a human with text, parts and usage information.

human_name_given

identifier

An identifier is a string associated with a single object or entity within a given system, typically used to connect content in resources to external content available in other frameworks or protocols

medication_concept

This table holds the primary keys of all unique medication concept groups. Individual codings within each concept group are in the medication_concept_coding table.

medication_concept_coding

This table holds the individual codings within each medication concept group. Each row in this table represents a single coding within a medication concept group.

route_concept

Representation of the route of which a drug should enter the body

route_concept_coding

Representation of a defined route concept using a symbol from a defined terminology system