Lost Time Import Tool
Covered by this topic
Must have security access to access the DATA IMPORT tab found in Control Panel sidemenu tab. The security needed is Allow .csv Data Import set to Yes. The default security is currently set to No for users.
If user(s) have security permission to allow .csv data import, then the user(s) can access the DATA IMPORT tab, this feature allows the user access to download a .csv template file and fill in patient demographic data using a spreadsheet application. If you have it set to NO, you can’t view or access the Data Import tab at all.
If your system does not have a Data Import tab, please contact your MIE Implementer to have the tab programmed on your system.
Once in the Data Import tab, use the drop down to select the specific Enterprise Health data import type and click the GO button.
Lost Time Import
In this help document we will be going through the Enterprise Health Lost Time import type.
Once you’ve made the drop-down selection from the Data Import tool type and clicked the GO button for Enterprise Health Lost Time import, you can download the.csv template file [Download Template ]. From your own downloaded copy, fill in your Lost Time data using a spreadsheet application.
This Enterprise Health import tool allows the creating of encounters and creation of cases/incidents in a patient’s chart with the data provided in the import spreadsheet.
Tip
Look at the CSV Lost Time Import Specification sheet to help identify what columns of recommended data and values to import. This is shareable information regarding more data, values, columns, spreadsheet example, etc.
Note
There are 5 different parts that could be imported regarding Lost Time. Not all 5 are needed, but each type has to be in its own separate unique spreadsheet file to import using this tool. Even though the template spreadsheet shows 5 tabs (one for each Encounters and Incidents, Patient Conditions, Patient Clinical Restriction, Accommodations, and Incident Body Parts) you must save each “type” into its own separate spreadsheet with only that tab of data. Do not have one spreadsheet with tabs for each import type (even though our spreadsheet template shows 5 tabs, please separate into specific unique individual files before importing).
INTERFACE allows you to specify which interface to store to find the patient.
VERBOSE mode will print out what the import is doing to the screen and the log file.
Template
You can view the spreadsheet template and download your own copy. Again, even though our template shows 5 tabs for each of the 5 types of Lost Time imports available, each must be on its own unique separate file when you go to import that type.
Data and Values for Encounters and Incidents
An encounter documents a visit with a patient, and is also known as a patient visit. An encounter is a template of specific items to be addressed, in part or completely, during a patient appointment.
A case/incident contains a full report of a workplace injury, or incident, for a patient (employee). Enterprise Health stores “cases/incidents” within an encounter. This import tool file would import/create encounters and cases/incidents.
| Column | Description | Length | Example |
| encounters.ext_id | Required Field External identifier–used for Enterprise Health systems. Typically populated by third party interfaces. | 30 | ABC123 or 54321 |
| encounters.patient_mrn. | Required Field Unique patient identifier. The value of this field will be the MRN in the partition defined by the column name.Replace with the partition to be used | 50 | 123456789 |
| encounters.visit_type | Recommended Field Description from the ‘encounter_visit_types' table. _What encounter visit type you want to be created when you import Lost Time. Must be the specific visit type code from your Enterprise Health system | 10 | Visit |
| encounters.priority | Configurable setting to set priority of encounter (client-specific use). | 10 | 1 |
| encounters.serv_date | Recommended Field Inserts the Date of Service for the encounter specified (when using encounters.visit_type field). If not indicated, the encounter will be created without a service date (will be blank).Must be in this date & time format: YYYY-MM-DD HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| encounters.discharge_date | Date discharged from hospital for inpatient care.Must be in YYYY-MM-DD format. | 19 | 2001-01-08 08:30:00 |
| encounters.comment | Free text comment regarding the encounter | Text | This encounter will be used for a Lost Time import |
| encounters.chief_complaint | Chief complaint of encounter (reason for visit). | Text | Here for consultation for diabetes, hypertension and GERD. |
| encounters.location | Location code. This is the ‘description' field from the Enterprise Health ‘location' manager | 60 | OFFICE |
| encounters.closed | Recommended Field Inserts the encounter visit type specified (when using encounters.visit_type field) as open or closed.Options include:
| 11 | 1 |
| encounters.stage | The current stage of encounter. | 40 | Intake |
| encounters.account_number | Often used for inpatient care for an external identifier tied to the encounter. | 30 | 123456 |
| encounters.due_date | Date encounter is due for panel action.Must be in YYYY-MM-DD format. | 19 | 2001-01-08 08:30:00 |
| incidents.inc_datetime | Required Field Maps to Enterprise Health incident field "Date & time of injury or onset of illness". Incident datetime.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.case_number | A string representing the incident. If a unique case id# from other system, indicate here. If not indicated, then Enterprise Health will not have a case # on the case/incident and will show "view" in that column. | 30 | ABC123 or 54321 |
| incidents.case_type | Recommended Field Maps to
Enterprise Health
incidents field named "Case Type". The type of case the incident refers to.Options include:* Injury-OSHA (would be value Injury)
| enumeration | Injury |
| incidents.facility_code | Facility location. This is the ‘description' field from the ‘locations' manager. | 60 | OFFICE |
| incidents.on_premises | Flags the incident if it occurred on employer's premises. Options include:
| 1 | 1 |
| incidents.loc_description | Recommended Field Description for a location that does not appear on the Enterprise Health locations table. | Text | CompanyABC Hospital |
| incidents.loc_address1 | Address 1 for a location that does not appear on the Enterprise Health locations table. | 50 | 123 Main Street |
| incidents.loc_address2 | Address 2 for a location that does not appear on the Enterprise Health locations table. | 50 | Apt 23 |
| incidents.loc_city | City for a location that does not appear on the Enterprise Health locations table. | 30 | Smallville |
| incidents.loc_state | State for a location that does not appear on the Enterprise Health locations table. | 3 | MN |
| incidents.loc_zip | Zip for a location that does not appear on the Enterprise Health locations table. | 11 | 12345 or 12345-6789 |
| incidents.loc_county | County for a location that does not appear on the Enterprise Health locations table. | 50 | Pima |
| incidents.loc_country | Country for a location that does not appear on the Enterprise Health locations table. | 30 | USA |
| incidents.hospitalized | Flag indicates if employee was hospitalized due to injury. Options include:
| 1 | 1 |
| incidents.emergency_room | Indicates if injury included an emergency room visit:Options include:
| 1 | 1 |
| incidents.treatment_loc_type | Maps to
Enterprise Health
field "Was treatment provided by". Location where employee/patient was treated. Options include:
| enumeration | External Provider |
| incidents.ohs_location | Onsite health services location. This is the ‘description' field from the ‘locations' manager. | 60 | OFFICE |
| incidents.hospital_name | Hospital name (if patient is hospitalized). | 50 | CompanyABC Hospital |
| incidents.hospital_address | Hospital address (if patient is hospitalized). | 100 | 123 Main Street |
| incidents.hospital_city | Hospital city (if patient is hospitalized). | 50 | Smallville |
| incidents.hospital_state | Hospital state (if patient is hospitalized). | 20 | MN |
| incidents.hospital_zip | Hospital zip (if patient is hospitalized). | 20 | 12345 or 12345-6789 |
| incidents.hospital_phone | Hospital phone (if patient is hospitalized). | 30 | 5558765309 |
| incidents.primary_physician | Name of patient's physician if outside of the company/facility. | 255 | John Brown |
| incidents.physician_address | Address of patient's physician if outside of the company/facility. | 100 | 123 Main Street |
| incidents.physician_city | City of patient's physician if outside of the company/facility. | 50 | Smallville |
| incidents.physician_phone | Phone of patient's physician if outside of the company/facility. | 20 | 5558765309 |
| incidents.osha_work_related | Recommended Field Maps to
Enterprise Health
incident field "Work Related". Flags injury as OSHA work-related. Options include:
| enumeration | Yes |
| incidents.osha_completed_dt | Recommended Field Maps to Enterprise Health incident field "Date determined recordable". Timestamp when incident was reported to OSHA.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.osha_itype | Recommended Field Maps to Enterprise Health incident field "Injury/illness type". Injury or illness type (OSHA list). Value choices: I=injury; S=skin disorder; R=respiratory condition; P=poisoning; H=hearing loss; A=all other illnesses | 65 | |
| incidents.privacy_case | Recommended Field Maps to
Enterprise Health
incident field "Privacy Case" checkbox. Flag if incident is sensitive. Name of employee is hidden on OSHA log. Options include:
| 1 | 1 |
| incidents.suppress_osha | Flag indicates if a record should be sent over an interface for OSHA reporting.Options include:
| 1 | 1 |
| incidents.workcomp_related | Recommended Field Maps to
Enterprise Health
incident field "Workers' comp related". Indicates that the incident is compensable by a work comp provider.Options include:
| enumeration | Yes |
| incidents.workcomp_completed_dt | Timestamp when ‘workcomp_related' status was determined. Used for communicating with work comp provider. | 19 | 2001-01-08 08:30:00 |
| incidents.workcomp_assigned_cm_dt | Datetime incident was assigned to a case manager. | 19 | 2001-01-08 08:30:00 |
| incidents.workcomp_first_contact_dt | Datetime the work comp case manager first makes contact with employee.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.hospital_discharge_dt | Datetime discharged from hospital.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.disability_begin_dt | Datetime designated disabled for work comp.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.workcomp_claim_reopen_dt | Datetime work comp case claim was reopened (if applicable).Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.workcomp_reported_to_carrier_dt | Datetime the work comp case manager reported the injury to the employee/patient's insurance company.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.return_to_work_dt | Maps to Enterprise Health incident field "Actual return to work date". Datetime employee returned to work post-injury.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.target_return_to_work_dt | Maps to Enterprise Health incident field "Expected return to work date". Goal datetime employee will return to work post-injury.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.last_treatment_dt | Datetime for last treatment for injury.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.initial_est_return_to_work_dt | Estimated datetime when employee will to return to work (if not working due to injury).Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.claimant_first_admitted_dt | Datetime if employee was admitted to hospital (for work comp)Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.date_last_worked | Recommended Field Maps to Enterprise Health incident field "Last date of work". Datetime the employee last time worked before the incident.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.days_away | Number of days employee was away from work (if applicable) due to injury. | 10 | 15 |
| incidents.days_restricted | Number of days a work restriction applies. | 10 | 30 |
| incidents.suppress_workcomp | Flag indicates if a record should be sent over an interface for work comp reporting.Options include:
| 1 | 1 |
| incidents.workcomp_claim_num | Work comp claim number from client (can be thru interface or documented manually). This maps to the Enterprise Health field "Claim Number" found in the incident/case summary section of an encounter for work comp. | 255 | ABC12345 |
| incidents.workcomp_contact | Name of work comp contact. Used for communicating with work comp provider. This maps to the Enterprise Health field "Adjuster/Examiner" found in the separate incident/case summary section of an encounter for work comp. | 255 | John Sample |
| incidents.workcomp_phone | Work comp provider phone number. This maps to the Enterprise Health field "Phone number" found in the separate incident/case summary section of an encounter for work comp. | 30 | 5558765309 |
| incidents.workcomp_fax | Work comp provider fax number. This maps to the Enterprise Health field "Fax number" found in the separate incident/case summary section of an encounter for work comp. | 30 | 5558765310 |
| incidents.workcomp_addr1 | Work comp provider address. This maps to the Enterprise Health field "Address" found in the separate incident/case summary section of an encounter for work comp. | 30 | 123 Main Street |
| incidents.workcomp_addr2 | Work comp provider address. This maps to the Enterprise Health field "Address2" found in the separate incident/case summary section of an encounter for work comp. | 30 | Apt 23 |
| incidents.workcomp_city | Work comp provider address. This maps to the Enterprise Health field "City" found in the separate incident/case summary section of an encounter for work comp. | 30 | Smallville |
| incidents.workcomp_state | Work comp provider address. This maps to the Enterprise Health field "State" found in the separate incident/case summary section of an encounter for work comp. | 4 | MN |
| incidents.workcomp_zip | Work comp provider address. This maps to the Enterprise Health field "Zip code" found in the separate incident/case summary section of an encounter for work comp. | 11 | 12345 or 12345-6789 |
| incidents.employee_starttime | Recommended Field Maps to
Enterprise Health
incident field "Time patient began work on day of injury/illness". Time employee began shift on day of injury.The following time formats are supported:
| 8 | 11:12:00AM |
| incidents.assigned_dept | Freetext department name. Documents the department the employee was in when the incident occurred. | 50 | DX535 |
| incidents.assigned_super | |||
| incidents.assigned_super_type | |||
| incidents.ppi | Percent permanent impairment–a disability rating:
| 1 | 1 |
| incidents.ppi_datetime | Datetime for PPI rating in ppi column.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.mmi | Maximum medical improvement (plateau):
| 1 | 1 |
| incidents.mmi_datetime | Datetime patient was declared improved (maximum medical improvement).Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.others_injured | Indicates if another employee was injured. Options:
| 1 | 1 |
| incidents.employee_died | Maps to
Enterprise Health
incidents field "Patient died". Indicates if employed died.Options:
| 1 | 0 |
| incidents.employee_deathdate | Datetime documented if the employee died due to injury.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.reported_super_datetime | Recommended Field Maps to Enterprise Health incident field "Date/time supervisor notified". Datetime incident was reported to the employee's supervisor.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.reported_ehs_datetime | Datetime injury was reported to health services.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.reported_by | |||
| incidents.reported_by_type | |||
| incidents.reported_by_title | Title of person who reported (employee). | 50 | Chief Architect |
| incidents.reported_by_phone | Phone number of person who reported the incident. | 30 | 5558765309 |
| incidents.reported_datetime | Datetime incident was reported. When manually creating a new case in Enterprise Health via an encounter in an employee's chart, the reported date assumes "current date/time" as the reported date in the background and this is displayed in view only on encounter and a column in the Common Case Report. There is no editable field in front-end of Enterprise Health for this reported date. If client has ability for their employee's to report incidents via their portal, it would be the date they reported it via the portal.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.comment_activity | Recommended Field Maps to Enterprise Health incidents field "What was the employee doing just before the incident occurred?" Documents action employee was performing before incident happened. Corresponds to OSHA form. | Text | Climbing a ladder |
| incidents.comment_explanation | Recommended Field Maps to Enterprise Health incident field "What happened?" Explanation of how injury occurred. Corresponds to OSHA form. | Text | When ladder slipped |
| incidents.comment_cause | Recommended Field Maps to Enterprise Health incident field "What object or substance directly harmed the employee?" Object or substance that harmed the employee. Corresponds to OSHA form. | Text | concrete floor |
| incidents.comments | Freetext comment on incident. | Text | This happened on the job while using a ladder. |
| incidents.status | Recommended Field Populates the "case/incident" in
Enterprise Health
as opened or closed. If bringing/importing in open cases, you want this value to be 1. Options include:
| 1 | 1 |
| incidents.conclusion_date | Datetime documents when incident ends.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incidents.outside_reported | Indicates if an injury was reported via outside source such as employee portal or physical therapist. Options:
| 1 | 0 |
| incidents.verified | If the incident was reported from outside of the organization, and needs to be verified internally. Options include:
| enumeration | Yes |
| incidents.witnesses | Freetext of witness names for witnesses of the incident. | Text | John Sample, Joe Butler |
| incidents.case_related_to_auto_accident | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_auto_accident_state | Used specifically for Kareo billing. | 4 | |
| incidents.case_related_to_employment | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_pregnancy | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_abuse | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_homebound | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_other | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_epsdt | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_epsdt_reason | Used specifically for Kareo billing. | 50 | |
| incidents.case_related_to_family_planning | Used specifically for Kareo billing. | 1 | |
| incidents.case_related_to_emergency | Used specifically for Kareo billing. | 1 | |
| incident_extended_fields.ca_dwc1_form | Recommended Field Maps to Enterprise Health incidents field "Date/time workers comp forms were given". Work comp form in California.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS | 19 | 2001-01-08 08:30:00 |
| incident_extended_fields.dc_dwdc7_form | DC work comp form. | 19 | 2001-01-08 08:30:00 |
| incident_extended_fields.workcomp_claim_type | [interface-specific use] | 100 | |
| incident_extended_fields.cause_of_injury | Maps to Enterprise Health incident field "CAUSE" dropdown. Object that caused injury (limited use). | 100 | |
| incident_extended_fields.nature_of_injury | Maps to Enterprise Health incident field "EVENT" dropdown. Type of injury (limited use). | 100 | |
| incident_extended_fields.location_claim_assigned_code | [interface-specific use] | 6 | |
| incident_extended_fields.location_loss_reported_code | [interface-specific use] | 2 | |
| incident_extended_fields.claimant_appeal_claim | [interface-specific use] | 1 | |
| incident_extended_fields.claimant_prior_injury | [interface-specific use] | 1 | |
| incident_extended_fields.modified_duty_at_insured | [interface-specific use] | 1 | |
| incident_extended_fields.workcomp_claim_reopened | [interface-specific use] | 1 | |
| incident_extended_fields.claimant_dept_name | [interface-specific use] | 15 | |
| incident_extended_fields.percent_perm_impairment_after_max_rx | [interface-specific use] | 7 | |
| incident_extended_fields.percent_perm_impairment_caused_by_injury | [interface-specific use] | 7 | |
| incident_extended_fields.prior_admin_code | [interface-specific use] | 10 | |
| incident_extended_fields.payment_demand_prior_carrier | [interface-specific use] | 13 | |
| incident_extended_fields.prior_admin_claim_key | [interface-specific use] | 10 | |
| incident_extended_fields.medical_service_provided | [interface-specific use] | 11 | |
| incident_extended_fields.coverage_provided_code | [interface-specific use] | 100 | |
| incident_extended_fields.surgery_medical_service | [interface-specific use] | 1 | |
| incident_extended_fields.workcomp_accident_desc | [interface-specific use] | 1 | |
| incident_extended_fields.resolution_status | How work comp claim was resolved. | 1 | |
| incident_extended_fields.claim_status | Flags claim as open or closed. | 50 | |
| incident_extended_fields.froi_refused | First report of injury refused (if patient refused services). | 1 |
Data and Values for Patient Conditions
This import tool file imports all details of a condition for a patient record. A condition is defined as a patient’s health/medical problems, frequently coded using SNOMED or ICD-9/10 Diagnosis codes.
| Column | Description | Length | Example |
| patient_conditions.ext_id | External identifier–used for Enterprise Health systems. Typically populated by third party interfaces. | 100 | DEF456 |
| patient_conditions.icd9 | ICD9 code for condition. | 15 | 427.81 |
| patient_conditions.icd10 | ICD10 code for condition. | 15 | E23.3 |
| patient_conditions.description | Freetext description of condition. | Text | The condition is causing some redness |
| patient_conditions.onset_date | Datetime of onset of condition. | 19 | 2001-01-08 08:30:00 |
| patient_conditions.conclusion_date | Datetime documents when condition ends. | 19 | 2001-01-08 08:30:00 |
| patient_conditions.notes | Notes regarding condition. | Text | The condition is pretty serious |
| patient_conditions.severity | Severity of condition - mild, moderate, severe. | 100 | moderate |
| patient_conditions.status | Status of condition (completed, etc.). | 11 | ongoing |
| patient_conditions.details | Freetext notes regarding condition. | 255 | The condition is pretty serious but getting better with treatment |
| patient_conditions.snomed | SNOMED code. | 15 | |
| patient_conditions.concept_id | SNOMED concept ID | 24 | |
| encounters.ext_id | External identifier that was used to import the encounter to which this condition applies | 100 | ABC123 |
Data and Values for Patient Clinical Restrictions
This import tool file imports restriction details. In occupational health, a restriction (clinical restriction) refers to an activity that an employee (patient) is not permitted to do after an injury (incident). An accommodation is a modification that allows an employee to continue working, or lost time (worker’s comp plan) available for an employee who cannot work after an incident.
| Column | Description | Length | Example |
| patient_clinical_restriction.ext_id | Required Field External identifier–used for Enterprise Health systems. Typically populated by third party interfaces. | 30 | XYZ987 |
| patient_clinical_restriction.description | This is the ‘description' column from the ‘clinical_restriction_types' Enterprise Health table. See the Specific Coded Values section for all specific options in the default product in the Lost Time CSV Import documentation. | Text | Accommodation |
| patient_clinical_restriction.type_option | Additional text for the description column. | 255 | Accommodation was at the local clinic |
| patient_clinical_restriction.type_option_label | If type option is a number, this is the unit of measurement. | 50 | |
| patient_clinical_restriction.allowed_weight | Identifies the number of pounds an injured employee can carry during a restriction. | 10 | 20 |
| patient_clinical_restriction.enforcing_provider | Text details of person who created restriction. | 255 | The clinic doctor |
| patient_clinical_restriction.active | Indicates if an entry is active:
| 1 | 1 |
| patient_clinical_restriction.start_date | Start date of the restriction | 19 | 2001-01-08 08:30:00 |
| patient_clinical_restriction.end_date | Conditionally Required Field End date of restriction. NOT needed if permanent | 19 | 2001-01-08 08:30:00 |
| patient_clinical_restriction.est_end_date | Datetime restriction is likely to end. | 19 | 2001-01-08 08:30:00 |
| patient_clinical_restriction.permanent | Conditionally Required Field Flags restriction as permanent (Not needed if end_date is set):
| 1 | 1 |
| patient_clinical_restriction.disability | Identifies the cause of a disability (if applicable). | 1 | The ladder slipped |
| patient_clinical_restriction.affect_work | Flag indicates the restriction affects the employee's work:
| 1 | 1 |
| patient_clinical_restriction.accommodated | Indicates if a restriction was completely accommodated.Options include:
| 1 | 1 |
| patient_clinical_restriction.occ_wc | Flags a restriction as work comp related. Options are:
| 1 | 1 |
| patient_clinical_restriction.create_date | Timestamp that entry was created. | 19 | 2001-01-08 08:30:00 |
| patient_clinical_restriction.comment | Freetext comment on restriction. | Text | This restriction only impacts forklift driving |
| encounters.ext_id | Required Field External identifier that was used to import the encounter to which this restriction applies | 100 | ABC123 |
| patient_conditions.ext_id | External identifier that was used to import the Patient Condition to which this restriction applies | 100 | DEF456 |
Data and Values for Accommodations
An accommodation is a modification that allows an employee to continue working, or lost time (worker’s comp plan) available for an employee who cannot work after an incident. This import tool file will import accommodation details for charts.
| Column | Description | Length | Example |
| accommodations.ext_id | Required Field External identifier–used for Enterprise Health systems. Typically populated by third party interfaces. | 100 | GHI789 |
| accommodations.accom_type | A description of the accommodation type.These are the specific choices/values for Accommodation Types:
| 255 | Work Location |
| accommodations.comments | Freetext comment on the way in which employee's job function is accommodated after an injury. | Text | Given a different job |
| accommodations.leader | The name of the individual overseeing the accommodation (likely a member of the worker's comp. team). | 100 | John Sample |
| accommodations.leader_id | |||
| accommodations.leader_id_type | |||
| accommodations.start_date | Datetime the accommodation begins. | 19 | 2001-01-08 08:30:00 |
| accommodations.end_date | Timestamp when the accommodation is over. | 19 | 2001-01-08 08:30:00 |
| accommodations.status | Status of accommodation.Options include:
| 10 | 1 |
| accommodations.create_date | Timestamp when the accommodation is made. | 19 | 2001-01-08 08:30:00 |
| patient_clinical_restriction.ext_id | External identifier that was used to import the patient clinical restriction to which this accommodation applies | 100 | XYZ987 |
| encounters.ext_id | Required Field External identifier that was used to import the encounter to which this accommodation applies | 100 | ABC123 |
Data and Values for Incident (Case) Body Parts
This imports (in the case/incident) the details for nature of injury, body parts, etc.
| Column | Description | Length | Example |
| incident_nibp.ext_id | Required Field External identifier–used for Enterprise Health systems. Typically populated by third party interfaces. It should be whatever uniquely id's the record in their other system so that later we can go back and say this record in Enterprise Health came from that record XX in their other system. If not known, can just insert incremental numbers in this column for each row to be unique. | 100 | HIT123 |
| incident_nibp.nature_injury | Required Field Text describing the nature of the injuryNOT required if ‘body_part' defined. | 255 | Abrasion/Cut/Puncture |
| incident_nibp.body_part | Required Field Text describing the body partNOT required if ‘nature_injury' defined | 255 | Head - Bilateral |
| incident_nibp.comment | Freetext comment about the nature of injury and body part. | Text | Puncture on the head due to a needle |
| incident_nibp.size | Size of the needle if the injury was a needlestick. | 255 | 12 |
| incident_nibp.manufacturer | Manufacturer of needle if nature of injury was needlestick. | 255 | ABC Company |
| incident_nibp.laceration | Used for needle sticks. Indicates if the stick was a laceration or puncture. Options include:
| enumeration | Laceration |
| encounters.ext_id | Required Field External identifier that was used to import the encounter to which this injury to body type applies | 100 | ABC123 |
Enterprise Health Documentation
Page Created:
Last Updated:
Last Build:
Sun, 13 Nov 2022 01:02:21 UTC
WikiGDrive Version: 8799ccfd58b47ed721e42eeadb589071776ed64f