Date handling

Date display—When dates appear in OutcomeLogix pages, the month is written out and not abbreviated, for example, 23/February/2012.

• The date format used in forms, audit trail pages, standard reports, and data extracts is the format defined in the user's profile and is based on date format configuration at the study, site, and user levels.
• In the audit trail, system dates are displayed in Greenwich Mean Time (GMT), and user-entered dates are displayed in the time zone of the user who entered them.
• Dates on clinical input forms appear exactly as entered. No conversion is made to show the dates in the current user's time zone.

Date storage—In the OutcomeLogix database:

• Clinical date times are stored in ISO 8601 format: YYYY-MM-DDTHH:MM:SS.
• Clinical dates are stored in ISO 8601 format: YYYY-MM-DD.
• No time zone is stored with date time components.

Partial dates—When either the day or month is unknown, but you know the year, you can select UNK MONTH or UNK DAY from a calendar view of a known year. For example, when entering medication dosing or adverse event start/stop dates, you usually know the year even if you do not know the month or day.

• Reporting—Standard and ad hoc reports display a hyphen (–) in place of unknown date parts. Ad hoc report writers should allow for the possibility of partial dates when constructing WHERE clauses that use dates.
• Data extracts—PDF extracts display a hyphen (–) in place of unknown date parts. Microsoft Excel extracts display dates using the date formats set as defaults or configured in the Microsoft Excel application.

Calendar controls—If the date field is blank, the calendar control displays the current year and month. If the date field contains data, the calendar control displays the values entered.

Note: A change (study patch) may be needed to implement this feature in your study.