Px Date

Data Element (edit)
Field Name:	Px Date
CCMDB Label:	Px Date
CCMDB tab:	CCI
Table:	L_CCI_Picklist table, L_CCI_Component table
Data type:	date
Length:	not stated
Program:	Med and CC
Created/Raw:	Raw
Start Date:	1988-07-11
End Date:	2300-01-01
Sort Index:	4

The date/time of a CCI procedure

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

The Px Date is coded as part of the CCI Collection.

• mandatory for procedures with Px Type acquired / Acquired Procedure
• not allowed for procedures with Px Type admit / Admit Procedure

Summary: We now enter a time for TISS PX Date on the day a pt moves to another unit so we can identify in which unit something happened. By the same reasoning, do we also need to do this for all other Px Date entries (CCI Pick or CCI component)? Ttenbergen 09:38, 2021 February 4 (CST) use the same rule for the rule for all procedure times as for TISS.

added: no added date action: no action date

• Cargo

• Categories

Limitations to field formatting

There have been requests to change this field so collectors don't need to actually type the punctuation components of the date and time. The time component is only needed when there is a second entry on a different unit for the same day (actually, so far it's only required for TISS, see discussion above).

A field can either be set up as a date, which enables the calendar popup, or with more flexible entry filters that would not require the punctuation, but not both. We chose to set the Px Date up in a way that enables the pop-up calendar but requires punctuation.

Discussed 2021-04-21 and decided to keep the default to show the calendar rather than simplify punctuation.

Data Integrity Checks (automatic list)

	App	Status
Query check CCI Date	CCMDB.accdb	implemented