Skip to content

Latest commit

 

History

History
159 lines (136 loc) · 7.77 KB

create-cases-file-for-import.md

File metadata and controls

159 lines (136 loc) · 7.77 KB
id title date version lastAuthor mimeType links source wikigdrive
12tRrL1GGMV0Hp0HQOhS4zdkbS1-fbnKf2kAroBdMqZc
Create Cases File for Import
2020-03-17T02:53:32.574Z
41
text/x-markdown
0008bcbb1563384efe0a28ada6f97e9432e65f10

This document explains how to import your cases into {{% system-name %}} .

What you will need:

  • Spreadsheet software (Microsoft Excel or Google Sheets)
  • Cases CSV File Example
  • {{% system-name %}} end user with administrative rights

Create Cases CSV File

  1. The following table provides optional or required Field Names and Descriptions, as indicated by the Requirement column. Items marked as Best Practice or Optional are not required and may be left blank, or omitted entirely. Employee ID must be the first column in the CSV file. The order of the remaining fields does not matter.
Field Name Description Requirement
Employee ID Employee Identifier Required
External ID This identifier will be used for looking up the chart in {{% system-name %}} , to insert or update, and must match an Employee ID from the Employee Demographic Import specification. Required
Visit Type Must be a specific visit type code from the {{% system-name %}} system. This is the visit type associated with the Clinical Encounter import. It is the Visit Type field taken from the Encounter Types manager. Best Practice
Date of Service Associated with encounter visit type, to insert the Date of Service (DOS) for the encounter specified. If a visit type is not indicated using encounters.visit_type field, the encounter will be created without a service date (i.e., it will be blank). DOS must be in YYYY-MM-DD HH:MM:SS format. Best Practice
Chief Complaint Reason for visit, or major complaint of an encounter. Best Practice
Service Location The location code for the document's service location. These are stored in the Locations Manager of the Control Panel. Best Practice
Case Closed Status Case Closed Status specifies whether or not the case is still active (i.e., open), or if the case has concluded (i.e., closed). Providing this field will insert the encounter as opened or closed. Valid options include:
    • 0 = Open
    • 1 = Closed
 Best Practice
Case Datetime Date and time of the case or incident. If an injury or illness accompanies the clinical encounter being imported, then a case should be created. Adding a Case Datetime creates a case in {{% system-name %}} and links the case to the clinical encounter. Must be formatted as YYYY-MM-DD HH:MM:SS Required for OSHA 300A Reporting & Best Practice for Illness / Injury Only
Case Type The type of case the incident refers to. Options include:
    • Injury = OSHA-related Injury cases
    • Hospital = Hospital cases
    • Billing = Billing cases
    • Absence Management = Absence management cases
    • MSEA = Medical Suitability for Expatriate Assignment cases
    • Medical Surveillance = Health Surveillance cases
 Best Practice
Incident Location Description Brief description where the incident occurred. For example, if it happened in Plant 4, the location description could be "Back truck dock". Best Practice
Work Related Flags injury as OSHA work-related:
    • 0 = No
    • 1 = Yes
    • 2 = Undetermined
 Best Practice
OSHA Reported Date Timestamp when incident was reported to OSHA. Date and time must be formatted as YYYY-MM-DD HH:MM:SS Best Practice
OSHA Injury/Illness Type Maps to the {{% sys-name %}} Injury/Illness Type incident field. Injury or illness type (OSHA list). Options include:
    • I = Injury
    • S = Skin disorder
    • R = Respiratory condition
    • P = Poisoning
    • H = Hearing loss
    • A = All other illnesses
 Best Practice
Privacy Case Flag if incident is sensitive. Name of employee is hidden on OSHA log.
    • 0 = No
    • 1 = Yes
 Best Practice
Incident Status Populates the case/incident in {{% sys-name %}} as opened or closed. If importing open cases, set this value to 1. Options include:
    • 2 = Closed
    • 1 = Current
    • 0 = Created, but not entered

{{% tip %}} For a more comprehensive list of supported fields, please refer to the Simplified Case Management CSV API Specification. {{% /tip %}}

  1. Using the table, above, determine the data to be imported. Starting with the Employee ID field, enter all required and desired data, verifying required data is present. Note that each row represents a case record. Below is a screenshot of the Cases CSV File Example for guidance.

  1. Save the file as CSV format.

Upload Injury Cases CSV File

  1. Login as a user with administrator rights.
  2. Navigate to the Control Panel from the side menu.

  1. Select the Data Import tab.

  1. Select Clinical Encounter CSV API from the drop-down menu and click Go.

  1. Select the Cases CSV File and click Upload.

{{% tip %}} For extra information on what happens during the import, click the Verbose* checkbox.* {{% /tip %}}

Resources

Troubleshooting

Ensure that all of the fields marked as Required have valid content. The file uploaded must be saved as a CSV formatted file. In case of any errors, contact Technical Support.