Page tree
Skip to end of metadata
Go to start of metadata

Orion Health processes the date and time as follows:

  • Server time is based on Coordinated Universal Time (UTC). 
  • Messages entering the system, without an offset, are assumed to be in UTC. 
  • For CDR, the time received can be given a default offset if it is not explicitly provided. The time is then converted to UTC and stored in CDR, along with the offset, so that the date and time information is normalized across all offsets.

Date and Time Format

YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]]+/-ZZZZ

Examples

20170812

201708120900

201708120900+0300

20170812090000.1234+0300

Components

The components of the date and time format can be interpreted as follows:

FieldDescriptionValues AcceptedUsage  ?

 

LengthGuidance

YYYY

Year

0000-9999
R4 

MM

Month

00-12
O2Only required for PID.7 and PID.29. See Special Cases.

DD

Day

00-last day of month
O2Only required for PID.7 and PID.29. See Special Cases.

HHMM

Hours and minutes

0000-2359
O4Represented in 24-hour notation.

SS

Seconds

00-59
O2 

.SSSS

Milliseconds

0-9999
O4

.1

.12

.1234

+/- ZZZZ

Offset from UTC

+/- 0000 - 1300
O5

Only required for MSH.7 Date Time of Message. Optional for all the other date and time fields in the HL7 message.

The first digit must be 0 or 1.

+0500

-1100

Health Domains and Downstream Systems

EMPI

EMPI does not accept the time zone offset values even if MSH.7 Date/Time of Message includes them. It uses the UTC time on the server to store messages instead. For Date of Birth and Date of Death, only the date is stored.

Relationships Store

By default, the date of entry into the database (UTC time on the server) is considered as the start date.

Clinical Data Spaces (CDS)

When CDS receives a CDA document, it stores any date and time fields, including offsets. No information is lost or truncated. For example:

Document date and time
<effectiveTime value="20130718120000-0800"/>
How CDS maps what it receives
<documentCreationTime>
    <startTimeMillis>1374177600000</startTimeMillis>
    <timeZoneId>-08:00</timeZoneId>
    <precision>SECOND</precision>
</documentCreationTime>
Response from FHIR API
(time is in UTC)
"dateAsserted": "2013-07-18T20:00:00+00:00"

Clinical Data Repository (CDR)

In CDR, when the C-CDA/C32 document is sent to Rhapsody for parsing into HL7, most of the offset information from the date and time fields are lost, except for Medications.

 

Health DomainDate and Time is stored in this HL7 or XML FieldInformation sent to CDR
Medications
substanceAdministration/effectiveTime
date + time (up to milliseconds) + offset
ProceduresPR1.5  Procedure Date/Time
PV1.44  Admit Date/Time
date
DemographicsMSH.7  Date/Time of Message
EVN.2  Recorded Date Time
date + time (up to seconds)
AllergiesAL1.6  Identification Datedate + time (up to seconds)

Special Cases

Date and Time Fields in the PID Segment

Partial dates for PID.7 Date/Time of Birth and PID.29 Date/Time of Death are not supported. These fields must contain the year, month, and day in the YYYYMMDD format. The time component is optional and is not processed. For example, 19491112.

Invalid Leap Day

When CDR encounters a leap day in a non-leap year, it rejects the leap day as an invalid date. For example, 20150229.



  • No labels