Px Date: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 18: Line 18:


== Moves ==<!-- this header is referenced by a template, if changing then resolve that as well -->
== Moves ==<!-- this header is referenced by a template, if changing then resolve that as well -->
In order to still be able to associate procedures and TISS entries with the location where they happen under [[PatientFollow Project]], we use the time component of the Px Date to link the Px to a [[Boarding Loc]].
{{DxPxDateTime Instructions}}
 
For a patient who moves on the day of the procedure, enter the Px Date that corresponds to the [[Boarding Loc]] where the pt was at the time of the procedure:
* if pt is in a location where they were already yesterday, or for the only [[Boarding Loc]] that day, use 0:00
* for a procedure that happened while at a new location that day, enter as Px Date the same DtTm as used for the current [[Boarding Loc]]
** if pt is at third location that day, use the third location's [[Boarding Loc]], etc
{{DiscussTask | 1
* There was an email exchange that people are not doing this consistently for all CCIs, especially in medicine. How should we do this going forward?
Whatever we do there will affect [[Check CCI CXR vs LOS]], so see that page as well for this discussion. [[User:Ttenbergen|Ttenbergen]] 15:50, 2021 September 2 (CDT)
}}


== Limitations to field formatting ==
== Limitations to field formatting ==

Latest revision as of 14:31, 2021 October 20

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.

Don't enter the time that a procedure was done, just the date. The time component should only be used for #Moves.

Moves

For Critical Care data collection

In order to still be able to associate dxs, procedures and TISS entries with the location where they happen under PatientFollow Project, we use the time component of the Date to link the Dx/Px to a Boarding Loc.

For a patient who moves on the day of the procedure or diagnosis, enter the date that corresponds to the Boarding Loc where the pt was at the time of the procedure:

  • if pt is in a location where they were already yesterday, or for the only Boarding Loc that day, use 0:00
  • for a procedure that happened while at a new location that day, enter as Px Date the same DtTm as used for the current Boarding Loc
    • if pt is at third location that day, use the third location's Boarding Loc, etc

For Medicine Data Collection

Enter the appropriate date, but leave the time as 0:00

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)

 AppStatus
Query check CCI DateCCMDB.accdbimplemented

Related Articles

Related articles: