MEDITECH Data Specification and Starter Query v3

[Deleted User]
[Deleted User] Posts: 0 👋
edited September 4 in Meditech

Version: v3

Release Date: Jan 24, 2023

Updated At Date: July 3, 2024

Introduction

This is the data specification for the information ControlCheck (formally known as Bluesight for Controlled Substances) requires for MEDITECH release integrations. ControlCheck ingests MEDITECH data from hospitals and dispensing data from the hospital’s automated dispensing cabinets. ControlCheck then compares the two sets of data to ensure that all dispenses of controlled substances have a corresponding administration for an equal amount.

Data Extract

Customers are strongly encouraged to use the starter query provided as the fastest path to a compliant data feed. The starter query can be found attached to this post below. This query has been validated to be effective for MEDITECH v5.67. Customers may opt to author their own query to extract the required data if the output meets the following data specification. The customer is solely responsible for any issues involving a custom query. If your hospital cannot meet the following data specification, please discuss this with your implementation specialist or contact help@bluesight.com.

ControlCheck_Starter_Query_V3.txt

File Transport

MEDITECH files can be uploaded via the ControlCheck user interface, however, delivery over SFTP is highly preferred. Most customers choose to transfer files once per day. File transfers are typically scheduled to occur after midnight and contain the previous day’s data. Data transfers should be scheduled after any ETL process has been completed.

Recommended file transfer times are from 0400-0600 to ensure 1) data has migrated to the appropriate servers and 2) that Bluesight is able to process files in a timely manner prior to customer auditing. Additionally, it is recommended that the EMR file be sent at least 30 minutes before the ADC file(s) for optimized processing and data ingestion.

Individual files should be generated per facility although there are certain use cases that would require including multiple facilities. Discuss with your implementation specialist before finalizing hospital groupings.

File Requirements

  • Files must be formatted with pipe-delimiters and as .csv that conform to RFC 4180 and utilize UTF-8 for character encoding
  • File size should not exceed 50 mb
  • The file name should follow the schema and can only contain letters, numbers, and underscores.
    • bluesight_healthsystem_hospitalname_meditech_admindate.csv
  • Output column headers are case sensitive and must match the values specified below. The order in which those columns appear can be different than the order listed below. However, it is highly recommended that customers follow the order below for consistency and readability.

Pre-Implementation & Data Validation

During implementation, your implementation specialist will request a historical extract of data. This is a one-time request that will be manually uploaded into the application. The historical file upload would not depend on the SFTP being fully setup. Potentially some requirements may be different during testing/validation such as file size, naming, and date range.

Data Fields

Output Column Name

Required

Data Type

Formating

Description

RX_Number

Y

Numeric

N/A

Order number

Prescription_ID

Y

Numeric

N/A

Prescription number

Drug_Mnemonic

Y

String

N/A

Unique medication identifier for the drug administered.

Drug_Description

Y

Varchar

Molecule(s), Concentration, Form Factor

Drug name for the drug that was administered. Should include molecule(s), concentration, and form factor.

Patient_Acct_Num

Y

Numeric

N/A

Unique ID of that patient encounter/visit number associated with the administration (i.e. financial information number).

Patient_MRN

Y

Numeric

N/A

Unique Medical Record Number patient identifier for the patient receiving the medication.

Patient_Name

Y

String

“Last Name,First Name” (includes quotes)

Name of the patient receiving the medication.

Admin_Date

Y

DateTime

ISO 8601 calendar dates and times with time zone designators; YYYY-MM-DD hh:mm:ss

Date the medication was administered as indicated by the provider.

Admin_Time

Y

DateTime

ISO 8601 calendar dates and times with time zone designators; YYYY-MM-DD hh:mm:ss

Time the medication was administered as indicated by the provider.

Admin_User_ID

Y

String

N/A

System login ID of the provider that administered the medication.

Admin_User_Name

Y

String

“First Name, Last Name” (includes quotes)

Name of the provider that administered the medication.

Admin_User_Role

Y

String

N/A

Role of the provider that administered the medication.

Given

Y

String

Y or N

Whether the medication was given or not.

Admin_Dose

Y

Numeric

N/A

The amount of drug administered.

Admin_Dose_Unit

Y

String

N/A

The unit of measure for the amount of drugs administered.

Facility

Y

String

N/A

The facility in which the medication was administered

Adm_Location

Y

String

N/A

The name of the location within the facility in which the medication was administered.

Adm_Unit

N

String

N/A

The sublocation of the medication being administered.

Undone

N

String

N/A

Value to determine if administration was not performed

Admin_Type

N

String

N/A

Type of Administration (ex. infusion)

Source_ID

N

String

N/A

The source of the administration order

Version Change Log

7/3/2024: Version 3 includes modular line for "Admin_Dose_Unit" if database value does not exist for Meditech Expanse.

Categories