Data Dictionary Tables
v_incident_report_personnel
Purpose Personnel response records for incidents. Relationships v_incident_report_apparatus: Many-to-One (N:1) Many personnel link to one apparatus response Referenced through incident_report_apparatus_id v_personnel: Many-to-One (N:1) Many responses ...
v_incident_report_people_insurance
Purpose Insurance information for incident-involved people. Relationships v_incident_report_people: Many-to-One (N:1) Many insurance records link to one person Referenced through incident_report_people_id v_personnel: Many-to-One (N:1) Many insurance ...
v_incident_report_people_address
Purpose Address records for incident-involved people. Relationships v_incident_report_people: Many-to-One (N:1) Many addresses link to one person Referenced through incident_report_people_id v_personnel: Many-to-One (N:1) Many addresses created by ...
v_incident_report_people
Purpose People involved in incidents. Relationships v_incident_report: Many-to-One (N:1) Many people link to one incident Referenced through incident_report_id v_incident_report_people_address: One-to-Many (1:N) One person can have many addresses ...
v_incident_report_payroll_summary
Purpose Incident-related payroll records. Relationships v_incident_report: Many-to-One (N:1) Many payroll records link to one incident Referenced through incident_report_id v_personnel: Many-to-One (N:1) Many payroll records link to one personnel ...
v_incident_report_apparatus
Purpose Apparatus response details for incidents. Relationships v_incident_report: Many-to-One (N:1) Many apparatus responses link to one incident Referenced through incident_report_id v_apparatus: Many-to-One (N:1) Many responses link to one ...
v_incident_action_taken
Purpose Incident response action records. Relationships v_incident_report: Many-to-Many (N:M) Many actions can be taken in many incidents Referenced through incident relationships Table Column Type Description rowkey integer Primary key action_id ...
v_hydrant_service_result
Purpose Hydrant service inspection results. Relationships v_hydrant_service: Many-to-One (N:1) Many results link to one service record Referenced through hydrant_service_id v_hydrant: Many-to-One (N:1) Many results link to one hydrant Referenced ...
v_fire_inspection_violation
Purpose Fire code violation records. Relationships f_fire_inspection: Many-to-One (N:1) Many violations link to one inspection Referenced through fire_inspection_id v_occupancy: Many-to-One (N:1) Many violations link to one location Referenced ...
v_fire_inspection_item_result
Purpose Fire inspection checklist results. Relationships f_fire_inspection: Many-to-One (N:1) Many results link to one inspection Referenced through fire_inspection_id v_personnel: Many-to-One (N:1) Many results created by one personnel Referenced ...
v_fire_dept_user
Purpose Fire department user information. Relationships v_personnel: One-to-One (1:1) One user links to one personnel record Referenced through id/user_id f_all_schedule: One-to-Many (1:N) One user can have many schedules Referenced through user_id ...
v_fire_burn_ban_area
Purpose Fire burn ban area tracking. Relationships v_cc_burn_permit: One-to-Many (1:N) One ban area can affect many permits Referenced through geographic relationship Table Column Type Description area_id integer Primary key area_name varchar(255) ...
v_fd_permit_plan_review
Purpose Permit plan review records. Relationships v_fd_permit: Many-to-One (N:1) Many reviews link to one permit Referenced through fd_permit_id v_personnel: Many-to-One (N:1) Many reviews assigned to one personnel Referenced through assigned_to ...
v_fd_permit
Purpose Fire department permit records. Relationships v_occupancy: Many-to-One (N:1) Many permits link to one location Referenced through address_id v_fd_permit_plan_review: One-to-Many (1:N) One permit can have many plan reviews Referenced through ...
v_event_payroll_summary
Purpose Event-related payroll records. Relationships v_event: Many-to-One (N:1) Many payroll records link to one event Referenced through event_id v_personnel: Many-to-One (N:1) Many payroll records link to one personnel Referenced through user_id ...
v_event_participant
Purpose Event participation tracking records. Relationships v_event: Many-to-One (N:1) Many participants link to one event Referenced through event_id v_personnel: Many-to-One (N:1) Many participants link to one personnel record Referenced through ...
v_event
Purpose Event records and tracking. Relationships v_event_participant: One-to-Many (1:N) One event can have many participants Referenced through event_id v_event_payroll_summary: One-to-Many (1:N) One event can have many payroll entries Referenced ...
v_equipment
Purpose Equipment inventory and tracking. Relationships v_work_order: One-to-Many (1:N) One equipment item can have many work orders Referenced through equipment_id v_asset_inspection_completed: One-to-Many (1:N) One equipment item can have many ...
v_epcr_vital
Purpose Patient vital signs records. Relationships f_epcr: Many-to-One (N:1) Many vitals link to one EPCR Referenced through epcr_id v_personnel: Many-to-One (N:1) Many vitals taken by one provider Referenced through vital_provider Table Column Type ...
v_epcr_signature
Purpose Electronic signature records for patient care reports. Relationships f_epcr: Many-to-One (N:1) Many signatures link to one EPCR Referenced through epcr_id Table Column Type Description id integer Primary key epcr_id integer EPCR reference ...
v_epcr_protocol
Purpose Patient care protocol records. Relationships f_epcr: Many-to-One (N:1) Many protocols link to one EPCR Referenced through epcr_id Table Column Type Description id integer Primary key epcr_id integer EPCR reference client_code varchar(28) ...
v_epcr_procedure
Purpose Patient care procedure records. Relationships f_epcr: Many-to-One (N:1) Many procedures link to one EPCR Referenced through epcr_id v_personnel: Many-to-One (N:1) Many procedures performed by one personnel Referenced through ...
v_epcr_medication
Purpose Current medication administration records. Relationships f_epcr: Many-to-One (N:1) Many medications link to one EPCR Referenced through epcr_id v_personnel: Many-to-One (N:1) Many medications administered by one personnel Referenced through ...
v_epcr_other_crew
Purpose Additional crew member records for patient care. Relationships f_epcr: Many-to-One (N:1) Many crew records link to one EPCR Referenced through epcr_id v_personnel: Many-to-One (N:1) Many crew records link to one personnel Referenced through ...
v_epcr_history_medication
Purpose Patient medication history records. Relationships f_epcr: Many-to-One (N:1) Many medication histories link to one EPCR Referenced through epcr_id v_epcr_history: Many-to-One (N:1) Many medications link to one history record Referenced through ...
v_epcr_history
Purpose Patient medical history records. Relationships f_epcr: Many-to-One (N:1) Many history records link to one EPCR Referenced through epcr_id v_epcr_history_medication: One-to-Many (1:N) One history record can have many medication records ...
v_epcr_exam
Purpose Patient examination records. Relationships f_epcr: Many-to-One (N:1) Many exams link to one EPCR Referenced through epcr_id v_epcr_vital: One-to-Many (1:N) One exam can have many vital sign records Referenced through timeline relationship ...
v_epcr_disposition_team
Purpose Patient care team disposition records. Relationships f_epcr: Many-to-One (N:1) Many dispositions link to one EPCR Referenced through epcr_id v_personnel: Many-to-Many (N:M) Many dispositions can involve many personnel Referenced through team ...
v_epcr_consumable
Purpose Tracks consumable items used during patient care. Relationships f_epcr: Many-to-One (N:1) Many consumables link to one EPCR Referenced through epcr_id f_asset_inventory: Many-to-One (N:1) Many consumables link to one inventory item Referenced ...
v_epcr_complaint
Purpose Patient complaint records from electronic patient care reports. Relationships f_epcr: Many-to-One (N:1) Many complaints link to one EPCR Referenced through epcr_id Table Column Type Description id integer Primary key epcr_id integer EPCR ...
v_dispatch
Purpose Emergency dispatch records view. Relationship v_incident_report: One-to-Many (1:N) One dispatch can have many incident reports Referenced through xref_id v_apparatus: Many-to-Many (N:M) Many dispatches can involve many apparatus Referenced ...
v_checklist_question_answers
Purpose Checklist completion records view. Relationships v_personnel: Many-to-One (N:1) Many answers link to one personnel Referenced through personnel_id v_equipment: Many-to-One (N:1) Many answers link to one equipment Referenced through asset ...
v_cc_smoke_alarm_request
Purpose Smoke alarm installation request view. Relationships v_occupancy: Many-to-One (N:1) Many requests link to one location Referenced through place_id v_personnel: Many-to-One (N:1) Many requests assigned to one personnel Referenced through ...
v_cc_functional_needs
Purpose Community functional needs registry view. Relationships v_occupancy: Many-to-One (N:1) Many functional needs records link to one location Referenced through address matching Table Column Type Description id integer Primary key name ...
v_cc_burn_permit_question
Purpose Burn permit questions and answers view. Relationships v_cc_burn_permit: Many-to-One (N:1) Many questions link to one permit Referenced through permit_id Table Column Type Description permit_answer_id integer Primary key question text Question ...
v_cc_burn_permit
Purpose Community burn permit records view. Relationships v_occupancy: Many-to-One (N:1) Many permits link to one location Referenced through place_id v_cc_burn_permit_question: One-to-Many (1:N) One permit can have many questions Referenced through ...
v_asset_inspection_completed
Purpose Completed asset inspection records view. Relationships v_apparatus: Many-to-One (N:1) Many inspections link to one apparatus Referenced through apparatus_id v_equipment: Many-to-One (N:1) Many inspections link to one equipment item Referenced ...
v_apparatus
Purpose Apparatus / vehicle information view. Relationships v_incident_report_apparatus: One-to-Many (1:N) One apparatus can be on many incident reports Referenced through apparatus_id v_fire_station: Many-to-One (N:1) Many apparatus belong to one ...
f_schedule
Purpose Personnel scheduling fact table. Relationships v_personnel: Many-to-One (N:1) Many schedules link to one personnel record Referenced through personnel_id v_fire_dept_user: Many-to-One (N:1) Many schedules link to one user Referenced through ...
f_incident_report
Purpose Documents emergency incidents and responses. Relationships f_epcr: One-to-Many (1:N) One incident can have multiple EPCRs Referenced through incident_report_id v_incident_report_apparatus: One-to-Many (1:N) One incident can have multiple ...
Next page