Px Date: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 20: Line 20:
* 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)? [[User:Ttenbergen|Ttenbergen]] 09:38, 2021 February 4 (CST)
* 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)? [[User:Ttenbergen|Ttenbergen]] 09:38, 2021 February 4 (CST)
}}
}}
== 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 {{PAGENAME}} up in a way that enables the pop-up calendar but requires punctuation.
{{Discuss|
* Would it be more valuable to not type punctuation but always have to type the date, or is it better to have to type the punctuation when a time is needed, but be able to pop-up enter the date most of the time.


== Data Integrity Checks ==
== Data Integrity Checks ==

Revision as of 13:37, 20 April 2021

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
Data Dependencies(Reports/Indicators/Data Elements): No results

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.

AJTT

  • 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)
  • SMW


  • 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.

{{Discuss|

  • Would it be more valuable to not type punctuation but always have to type the date, or is it better to have to type the punctuation when a time is needed, but be able to pop-up enter the date most of the time.


Data Integrity Checks

Related Articles

Related articles: