LAU OT/PT consults: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 16: | Line 16: | ||
For every [[LAU Collection Project]], a line with Project = "Consults" and item = "not entered" will automatically be entered. Update that line to one of the following: | For every [[LAU Collection Project]], a line with Project = "Consults" and item = "not entered" will automatically be entered. Update that line to one of the following: | ||
* '''Project: OTPT Consults''' - Item: "OT First" | * '''Project: OTPT Consults''' - Item: "OT First" | ||
* '''Project: Consults''' - Item: "PT First" | * '''Project: OTPT Consults''' - Item: "PT First" | ||
* '''Project: Consults''' - Item: "PT Last" | * '''Project: OTPT Consults''' - Item: "PT Last" | ||
* '''Project: Consults''' - Item: "PT Last" | * '''Project: OTPT Consults''' - Item: "PT Last" | ||
* '''Project: Consults''' - Item: "no consult" (cross-check item if there were no consults) | * '''Project: OTPT Consults''' - Item: "no consult" (cross-check item if there were no consults) | ||
* Date/Time: dttm of the consult | * Date/Time: | ||
** dttm of the consult | |||
** [[Service tmp entry]] for first consult if pt arrived with a consult in progress | |||
{{DL| Or do we want to be able to enter actual?}} | |||
{{DL | Do we want an instruction if sign-off isn't found? }} | |||
{{DL | Do we want that cross-check entry? Do we need one for each or is a simple "no consult" if there is neither consult sufficient? | |||
{{DL | Are these common enough that you;d want an automated "not entered" entry?}} | |||
* Checkbox, Integer, Real, Comment: not used | * Checkbox, Integer, Real, Comment: not used | ||
Revision as of 00:51, 12 March 2025
| Projects | |
| Active?: | planned |
| Program: | |
| Requestor: | Dr. Nick Hajidiacos |
| Collection start: | Whenever LAU Collection Project starts "Whenever LAU Collection Project starts" contains an extrinsic dash or other characters that are invalid for a date interpretation. |
| Collection end: | Whenever [LAU Collection Project]] is done "Whenever [LAU Collection Project]] is done" contains an extrinsic dash or other characters that are invalid for a date interpretation. |
This dataset contains data in support of the LAU Collection Project.
The time that OT and PT are consulted and the time they sign off on a discharge.
Data Collection
- For any record collected as part of LAU Collection Project, enter the date and time of the first OT and PT consultx and the last sign-off by each discipline
Data Entry Instructions
For every LAU Collection Project, a line with Project = "Consults" and item = "not entered" will automatically be entered. Update that line to one of the following:
- Project: OTPT Consults - Item: "OT First"
- Project: OTPT Consults - Item: "PT First"
- Project: OTPT Consults - Item: "PT Last"
- Project: OTPT Consults - Item: "PT Last"
- Project: OTPT Consults - Item: "no consult" (cross-check item if there were no consults)
- Date/Time:
- dttm of the consult
- Service tmp entry for first consult if pt arrived with a consult in progress
|
Or do we want to be able to enter actual? |
|
|
Do we want an instruction if sign-off isn't found? |
{{DL | Do we want that cross-check entry? Do we need one for each or is a simple "no consult" if there is neither consult sufficient?
|
|
Are these common enough that you;d want an automated "not entered" entry? |
- Checkbox, Integer, Real, Comment: not used
Sources
- Orders
- consult section
- progress notes
- EPR ER notes/documents
Data Use
This data is being collected as a current state for LAU Collection Project.
Data Integrity Checks (automatic list)
none found
Background
- When we realized we would do Project Consults data we contacted Nick whether we want additional consults, and possibly for other than LAU.
- he would like OT/PT first consult and when they sign off Lisa Kaita 21:03, 10 March 2025 (CDT)
- decision made to break out the LAU OT/PT consults to a separate project
- considered and decided that we will not include SLP, mostly so we can get started with the project rather get delayed further waiting for an answer
Related articles
| Related articles: |