EPR Admit DtTm field
Legacy Content
This page contains Legacy Content.- Explanation: This is a legacy data field, its DataElementEndDate is in the past.
- Successor: No successor was entered
Click Expand to show legacy content.
| Data Element (edit) | |
| Field Name: | EPR_Admit_DtTm |
| CCMDB Label: | EPR Admit DtTm |
| CCMDB tab: | not stated |
| Table: | L_Log table |
| Data type: | date |
| Length: | not stated |
| Program: | Med and CC |
| Created/Raw: | Raw |
| Start Date: | 2019-10-27 |
| End Date: | 2020-11-01 |
| Sort Index: | 42 |
arrival time on the unit as per Cognos/ EPR data
Legacy Content
This page contains Legacy Content.- Explanation: field was used to match data with EPR Reports Integrator; we tried to use it with Cognos EPR Report but it really wasn't suitable for that any longer once we moved to Cognos2 and Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry
- Successor: Boarding Loc, Service tmp entry
Click Expand to show legacy content.
Collection Instruction
The field does not need to be manually entered.
The field contains the arrival time on the unit as per Cognos/ EPR data, and this data is automatically added by the Cognos Admitter / EPR Reports Integrator.
The EPR Reports Integrator need to be able to identify Cognos records for which L_Log records already exist. This means comparing the arrive times in L_Log and in Cognos. However, we sometimes use a different definition for Arrive DtTm (See that page for details) so a comparison to that would not work.
The only reason the field is listed in CCMDB.accdb is to be able to understand linking to EPR Reports Integrator.
Data Use
The data isn't used after the patient has been sent, it is purely operational to allow comparison with the EPR Reports Integrator.
Data Integrity Checks
Data Integrity Checks (automatic list)
none found
Related articles
| Related articles: |
|