Lost Time Import Tool

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 WebChart data import type and click the GO button.

Lost Time Import

In this help document we will be going through the WebChart Lost Time import type.

Once you’ve made the drop-down selection from the Data Import tool type and clicked the GO button for WebChart 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 WebChart 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). WebChart stores “cases/incidents” within an encounter. This import tool file would import/create encounters and cases/incidents.

ColumnDescriptionLengthExample
encounters.ext_idRequired Field External identifier–used for WebChart systems. Typically populated by third party interfaces.30ABC123 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 used50123456789
encounters.visit_typeRecommended 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 WebChart system10Visit
encounters.priorityConfigurable setting to set priority of encounter (client-specific use).101
encounters.serv_dateRecommended 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:SS192001-01-08 08:30:00
encounters.discharge_dateDate discharged from hospital for inpatient care.Must be in YYYY-MM-DD format.192001-01-08 08:30:00
encounters.commentFree text comment regarding the encounterTextThis encounter will be used for a Lost Time import
encounters.chief_complaintChief complaint of encounter (reason for visit).TextHere for consultation for diabetes, hypertension and GERD.
encounters.locationLocation code.  This is the ‘description' field from the WebChart ‘location' manager60OFFICE
encounters.closedRecommended Field Inserts the encounter visit type specified (when using encounters.visit_type field) as open or closed.Options include:
  • 0 (would be value Open)

  • 1 (would be value Closed)

111
encounters.stageThe current stage of encounter.40Intake
encounters.account_numberOften used for inpatient care for an external identifier tied to the encounter.30123456
encounters.due_dateDate encounter is due for panel action.Must be in YYYY-MM-DD format.192001-01-08 08:30:00
incidents.inc_datetimeRequired Field Maps to WebChart 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:SS192001-01-08 08:30:00
incidents.case_numberA string representing the incident. If a unique case id# from other system, indicate here. If not indicated, then WebChart will not have a case # on the case/incident and will show "view" in that column.30ABC123 or 54321
incidents.case_typeRecommended Field Maps to WebChart incidents field named "Case Type". The type of case the incident refers to.Options include:* Injury-OSHA (would be value Injury)
  • Injury NON-OSHA (would be value Injury NO)

  • Hospital (would be value Hospital)

  • Billing (would be value Billing)

  • Absence management (would be value Absence management)

  • MSEA (would be value MSEA)

enumerationInjury
incidents.facility_codeFacility location.  This is the ‘description' field from the ‘locations' manager.60OFFICE
incidents.on_premisesFlags the incident if it occurred on employer's premises. Options include:
  • 1 - yes

  • 0 - no

11
incidents.loc_descriptionRecommended Field Description for a location that does not appear on the WebChart locations table.TextCompanyABC Hospital
incidents.loc_address1Address 1 for a location that does not appear on the WebChart locations table.50123 Main Street
incidents.loc_address2Address 2 for a location that does not appear on the WebChart locations table.50Apt 23
incidents.loc_cityCity for a location that does not appear on the WebChart locations table.30Smallville
incidents.loc_stateState for a location that does not appear on the WebChart locations table.3MN
incidents.loc_zipZip for a location that does not appear on the WebChart locations table.1112345 or 12345-6789
incidents.loc_countyCounty for a location that does not appear on the WebChart locations table.50Pima
incidents.loc_countryCountry for a location that does not appear on the WebChart locations table.30USA
incidents.hospitalizedFlag indicates if employee was hospitalized due to injury. Options include:
  • 1 - yes

  • 0 - no

11
incidents.emergency_roomIndicates if injury included an emergency room visit:Options include:
  • 1 - yes

  • 0 - no

11
incidents.treatment_loc_typeMaps to WebChart field "Was treatment provided by". Location where employee/patient was treated. Options include:
  • Onsite Health Services

  • ER

  • External Provider

  • Other

enumerationExternal Provider
incidents.ohs_locationOnsite health services location.  This is the ‘description' field from the ‘locations' manager.60OFFICE
incidents.hospital_nameHospital name (if patient is hospitalized).50CompanyABC Hospital
incidents.hospital_addressHospital address (if patient is hospitalized).100123 Main Street
incidents.hospital_cityHospital city (if patient is hospitalized).50Smallville
incidents.hospital_stateHospital state (if patient is hospitalized).20MN
incidents.hospital_zipHospital zip (if patient is hospitalized).2012345 or 12345-6789
incidents.hospital_phoneHospital phone (if patient is hospitalized).305558765309
incidents.primary_physicianName of patient's physician if outside of the company/facility.255John Brown
incidents.physician_addressAddress of patient's physician if outside of the company/facility.100123 Main Street
incidents.physician_cityCity of patient's physician if outside of the company/facility.50Smallville
incidents.physician_phonePhone of patient's physician if outside of the company/facility.205558765309
incidents.osha_work_relatedRecommended Field Maps to WebChart incident field "Work Related". Flags injury as OSHA work-related. Options include:
  • Yes

  • No

  • Undetermined

  • N/A

enumerationYes
incidents.osha_completed_dtRecommended Field Maps to WebChart 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:SS192001-01-08 08:30:00
incidents.osha_itypeRecommended Field Maps to WebChart 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 illnesses65
incidents.privacy_caseRecommended Field Maps to WebChart incident field "Privacy Case" checkbox. Flag if incident is sensitive. Name of employee is hidden on OSHA log. Options include:
  • 1 - yes

  • 0 - no

11
incidents.suppress_oshaFlag indicates if a record should be sent over an interface for OSHA reporting.Options include:
  • 1 - do not send over interface

  • 2 - send over interface

  • 0 - send send over interface to safety system for OSHA reporting that is separate from WebChart

11
incidents.workcomp_relatedRecommended Field Maps to WebChart incident field "Workers' comp related". Indicates that the incident is compensable by a work comp provider.Options include:
  • Yes

  • No

  • Undetermined

  • N/A

enumerationYes
incidents.workcomp_completed_dtTimestamp when ‘workcomp_related' status was determined. Used for communicating with work comp provider.192001-01-08 08:30:00
incidents.workcomp_assigned_cm_dtDatetime incident was assigned to a case manager.192001-01-08 08:30:00
incidents.workcomp_first_contact_dtDatetime 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:SS192001-01-08 08:30:00
incidents.hospital_discharge_dtDatetime discharged from hospital.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.disability_begin_dtDatetime designated disabled for work comp.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.workcomp_claim_reopen_dtDatetime work comp case claim was reopened (if applicable).Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.workcomp_reported_to_carrier_dtDatetime 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:SS192001-01-08 08:30:00
incidents.return_to_work_dtMaps to WebChart 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:SS192001-01-08 08:30:00
incidents.target_return_to_work_dtMaps to WebChart 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:SS192001-01-08 08:30:00
incidents.last_treatment_dtDatetime for last treatment for injury.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.initial_est_return_to_work_dtEstimated 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:SS192001-01-08 08:30:00
incidents.claimant_first_admitted_dtDatetime if employee was admitted to hospital (for work comp)Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.date_last_workedRecommended Field Maps to WebChart 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:SS192001-01-08 08:30:00
incidents.days_awayNumber of days employee was away from work (if applicable) due to injury.1015
incidents.days_restrictedNumber of days a work restriction applies.1030
incidents.suppress_workcompFlag indicates if a record should be sent over an interface for work comp reporting.Options include:
  • 1 - do not send over interface

  • 2 - send over interface

  • 0 - send send over interface to safety system for work comp reporting that is separate from WebChart

11
incidents.workcomp_claim_numWork comp claim number from client (can be thru interface or documented manually). This maps to the WebChart field "Claim Number" found in the incident/case summary section of an encounter for work comp.255ABC12345
incidents.workcomp_contactName of work comp contact. Used for communicating with work comp provider. This maps to the WebChart field "Adjuster/Examiner" found in the separate incident/case summary section of an encounter for work comp.255John Sample
incidents.workcomp_phoneWork comp provider phone number. This maps to the WebChart field "Phone number" found in the separate incident/case summary section of an encounter for work comp.305558765309
incidents.workcomp_faxWork comp provider fax number. This maps to the WebChart field "Fax number" found in the separate incident/case summary section of an encounter for work comp.305558765310
incidents.workcomp_addr1Work comp provider address. This maps to the WebChart field "Address" found in the separate incident/case summary section of an encounter for work comp.30123 Main Street
incidents.workcomp_addr2Work comp provider address. This maps to the WebChart field "Address2" found in the separate incident/case summary section of an encounter for work comp.30Apt 23
incidents.workcomp_cityWork comp provider address. This maps to the WebChart field "City" found in the separate incident/case summary section of an encounter for work comp.30Smallville
incidents.workcomp_stateWork comp provider address. This maps to the WebChart field "State" found in the separate incident/case summary section of an encounter for work comp.4MN
incidents.workcomp_zipWork comp provider address. This maps to the WebChart field "Zip code" found in the separate incident/case summary section of an encounter for work comp.1112345 or 12345-6789
incidents.employee_starttimeRecommended Field Maps to WebChart 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:
  • HH:MM:SS

  • HH:MM:SSAM

  • HH:MM:SSPM

811:12:00AM
incidents.assigned_deptFreetext department name. Documents the department the employee was in when the incident occurred.50DX535
incidents.assigned_super
incidents.assigned_super_type
incidents.ppiPercent permanent impairment–a disability rating:
  • 1 - yes

  • 0 - no

11
incidents.ppi_datetimeDatetime for PPI rating in ppi column.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.mmiMaximum medical improvement (plateau):
  • 1 - yes

  • 0 - no

11
incidents.mmi_datetimeDatetime patient was declared improved (maximum medical improvement).Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.others_injuredIndicates if another employee was injured. Options:
  • 1 - yes

  • 0 - no

11
incidents.employee_diedMaps to WebChart incidents field "Patient died". Indicates if employed died.Options:
  • 1 - yes

  • 0 - no

10
incidents.employee_deathdateDatetime documented if the employee died due to injury.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.reported_super_datetimeRecommended Field Maps to WebChart 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:SS192001-01-08 08:30:00
incidents.reported_ehs_datetimeDatetime injury was reported to health services.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.reported_by
incidents.reported_by_type
incidents.reported_by_titleTitle of person who reported (employee).50Chief Architect
incidents.reported_by_phonePhone number of person who reported the incident.305558765309
incidents.reported_datetimeDatetime incident was reported. When manually creating a new case in WebChart 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 WebChart 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:SS192001-01-08 08:30:00
incidents.comment_activityRecommended Field Maps to WebChart incidents field "What was the employee doing just before the incident occurred?" Documents action employee was performing before incident happened. Corresponds to OSHA form.TextClimbing a ladder
incidents.comment_explanationRecommended Field Maps to WebChart incident field "What happened?" Explanation of how injury occurred. Corresponds to OSHA form.TextWhen ladder slipped
incidents.comment_causeRecommended Field Maps to WebChart incident field "What object or substance directly harmed the employee?" Object or substance that harmed the employee. Corresponds to OSHA form.Textconcrete floor
incidents.commentsFreetext comment on incident.TextThis happened on the job while using a ladder.
incidents.statusRecommended Field Populates the "case/incident" in WebChart as opened or closed. If bringing/importing in open cases, you want this value to be 1. Options include:
  • 1 - current

  • 2 - closed

  • 0 - created but not entered

11
incidents.conclusion_dateDatetime documents when incident ends.Must be in date format of YYYY-MM-DD and time format of HH:MM:SS192001-01-08 08:30:00
incidents.outside_reportedIndicates if an injury was reported via outside source such as employee portal or physical therapist. Options:
  • 1 - yes

  • 0 - no

10
incidents.verifiedIf the incident was reported from outside of the organization, and needs to be verified internally. Options include:
  • No

  • Yes

  • Declined

enumerationYes
incidents.witnessesFreetext of witness names for witnesses of the incident.TextJohn Sample, Joe Butler
incidents.case_related_to_auto_accidentUsed specifically for Kareo billing.1
incidents.case_related_to_auto_accident_stateUsed specifically for Kareo billing.4
incidents.case_related_to_employmentUsed specifically for Kareo billing.1
incidents.case_related_to_pregnancyUsed specifically for Kareo billing.1
incidents.case_related_to_abuseUsed specifically for Kareo billing.1
incidents.case_related_to_homeboundUsed specifically for Kareo billing.1
incidents.case_related_to_otherUsed specifically for Kareo billing.1
incidents.case_related_to_epsdtUsed specifically for Kareo billing.1
incidents.case_related_to_epsdt_reasonUsed specifically for Kareo billing.50
incidents.case_related_to_family_planningUsed specifically for Kareo billing.1
incidents.case_related_to_emergencyUsed specifically for Kareo billing.1
incident_extended_fields.ca_dwc1_formRecommended Field Maps to WebChart 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:SS192001-01-08 08:30:00
incident_extended_fields.dc_dwdc7_formDC work comp form.192001-01-08 08:30:00
incident_extended_fields.workcomp_claim_type[interface-specific use]100
incident_extended_fields.cause_of_injuryMaps to WebChart incident field "CAUSE" dropdown. Object that caused injury (limited use).100
incident_extended_fields.nature_of_injuryMaps to WebChart 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_statusHow work comp claim was resolved.1
incident_extended_fields.claim_statusFlags claim as open or closed.50
incident_extended_fields.froi_refusedFirst 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.

ColumnDescriptionLengthExample
patient_conditions.ext_idExternal identifier–used for WebChart systems. Typically populated by third party interfaces.100DEF456
patient_conditions.icd9ICD9 code for condition.15427.81
patient_conditions.icd10ICD10 code for condition.15E23.3
patient_conditions.descriptionFreetext description of condition.TextThe condition is causing some redness
patient_conditions.onset_dateDatetime of onset of condition.192001-01-08 08:30:00
patient_conditions.conclusion_dateDatetime documents when condition ends.192001-01-08 08:30:00
patient_conditions.notesNotes regarding condition.TextThe condition is pretty serious
patient_conditions.severitySeverity of condition - mild, moderate, severe.100moderate
patient_conditions.statusStatus of condition (completed, etc.).11ongoing
patient_conditions.detailsFreetext notes regarding condition.255The condition is pretty serious but getting better with treatment
patient_conditions.snomedSNOMED code.15 
patient_conditions.concept_idSNOMED concept ID24 
encounters.ext_idExternal identifier that was used to import the encounter to which this condition applies100ABC123

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.

ColumnDescriptionLengthExample
patient_clinical_restriction.ext_idRequired Field External identifier–used for WebChart systems. Typically populated by third party interfaces.30XYZ987
patient_clinical_restriction.descriptionThis is the ‘description' column from the ‘clinical_restriction_types' WebChart table. See the Specific Coded Values section for all specific options in the default product in the Lost Time CSV Import documentation.TextAccommodation
patient_clinical_restriction.type_optionAdditional text for the description column.255Accommodation was at the local clinic
patient_clinical_restriction.type_option_labelIf type option is a number, this is the unit of measurement.50 
patient_clinical_restriction.allowed_weightIdentifies the number of pounds an injured employee can carry during a restriction.1020
patient_clinical_restriction.enforcing_providerText details of person who created restriction.255The clinic doctor
patient_clinical_restriction.activeIndicates if an entry is active:
  • 0 - no

  • 1 - yes

  • 2 - previously revised

11
patient_clinical_restriction.start_dateStart date of the restriction192001-01-08 08:30:00
patient_clinical_restriction.end_dateConditionally Required Field End date of restriction. NOT needed if permanent192001-01-08 08:30:00
patient_clinical_restriction.est_end_dateDatetime restriction is likely to end.192001-01-08 08:30:00
patient_clinical_restriction.permanentConditionally Required Field Flags restriction as permanent (Not needed if end_date is set):
  • 1 - yes or

  • 0 - no  (no end date on restriction)

11
patient_clinical_restriction.disabilityIdentifies the cause of a disability (if applicable).1The ladder slipped
patient_clinical_restriction.affect_workFlag indicates the restriction affects the employee's work:
  • 1 - yes or

  • 0 - no

11
patient_clinical_restriction.accommodatedIndicates if a restriction was completely accommodated.Options include:
  • 0 - not accommodated

  • 1 - fully accommodated

  • 2 - currently accommodated

11
patient_clinical_restriction.occ_wcFlags a restriction as work comp related. Options are:
  • 1 - yes or

  • 0 - no

11
patient_clinical_restriction.create_dateTimestamp that entry was created.192001-01-08 08:30:00
patient_clinical_restriction.commentFreetext comment on restriction.TextThis restriction only impacts forklift driving
encounters.ext_idRequired Field External identifier that was used to import the encounter to which this restriction applies100ABC123
patient_conditions.ext_idExternal identifier that was used to import the Patient Condition to which this restriction applies100DEF456

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.

ColumnDescriptionLengthExample
accommodations.ext_idRequired Field External identifier–used for WebChart systems. Typically populated by third party interfaces.100GHI789
accommodations.accom_typeA description of the accommodation type.These are the specific choices/values for Accommodation Types:
  • Work Location

  • Transitional Duty

  • TDP-Work Area

  • Housing

  • Lost Time/Occ

  • Lost Time/Non-Occ

  • Lost Time/Maternity (CA)

  • Lost Time/ER LAT Approved

  • Lost Time

255Work Location
accommodations.commentsFreetext comment on the way in which employee's job function is accommodated after an injury.TextGiven a different job
accommodations.leaderThe name of the individual overseeing the accommodation (likely a member of the worker's comp. team).100John Sample
accommodations.leader_id   
accommodations.leader_id_type   
accommodations.start_dateDatetime the accommodation begins.192001-01-08 08:30:00
accommodations.end_dateTimestamp when the accommodation is over.192001-01-08 08:30:00
accommodations.statusStatus of accommodation.Options include:
  • 0 - deleted

  • 1 - active

  • 2 - revised

101
accommodations.create_dateTimestamp when the accommodation is made.192001-01-08 08:30:00
patient_clinical_restriction.ext_idExternal identifier that was used to import the patient clinical restriction to which this accommodation applies100XYZ987
encounters.ext_idRequired Field External identifier that was used to import the encounter to which this accommodation applies100ABC123

Data and Values for Incident (Case) Body Parts

This imports (in the case/incident) the details for nature of injury, body parts, etc.

ColumnDescriptionLengthExample
incident_nibp.ext_idRequired Field External identifier–used for WebChart 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 WebChart 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.100HIT123
incident_nibp.nature_injuryRequired Field Text describing the nature of the injuryNOT required if ‘body_part' defined.255Abrasion/Cut/Puncture
incident_nibp.body_partRequired Field Text describing the body partNOT required if ‘nature_injury' defined255Head - Bilateral
incident_nibp.commentFreetext comment about the nature of injury and body part.TextPuncture on the head due to a needle
incident_nibp.sizeSize of the needle if the injury was a needlestick.25512
incident_nibp.manufacturerManufacturer of needle if nature of injury was needlestick.255ABC Company
incident_nibp.lacerationUsed for needle sticks. Indicates if the stick was a laceration or puncture. Options include:
  • Laceration

  • Puncture

enumerationLaceration
encounters.ext_idRequired Field External identifier that was used to import the encounter to which this injury to body type applies100ABC123

WebChart Documentation

Page Created:
Last Updated:
Last Build: Mon, 14 Nov 2022 01:22:36 EST
WikiGDrive Version: 64fa77a2dd4586094b6074a78ed6769886b60894