ClientVisitGUID field: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
|field_name=ClientVisitGUID | |field_name=ClientVisitGUID | ||
|CCMDB_label=N/A | |CCMDB_label=N/A | ||
|in_table= | |in_table=L_Log table | ||
|data_type=string | |data_type=string | ||
|datafield_length=16 | |datafield_length=16 | ||
|program_collecting=Med and CC | |program_collecting=Med and CC | ||
|created_raw=Raw | |created_raw=Raw | ||
|data_element_start_date = | |data_element_start_date=2022-08-29 | ||
|data_element_sort_index=1 | |data_element_sort_index=1.6 | ||
|element_description=Unique identifier of a hospital admission for a patient for use with multiple encounters and Cognos data. | |element_description=Unique identifier of a hospital admission for a patient for use with multiple encounters and Cognos data. | ||
}} | }} | ||
The {{PAGENAME}} is the identifier used in [[Cognos]] to designate a hospitalization. We collect it to help deal with multiple encounters (eg see also [[Hospitalization ID]], [[Visit Admit DtTm]]) and with uniquely matching components of Cognos data to profiles. | The {{PAGENAME}} is the identifier used in [[Cognos]] to designate a hospitalization. We collect it to help deal with multiple encounters (eg see also [[Hospitalization ID]], [[Visit Admit DtTm]]) and with uniquely matching components of Cognos data to profiles. | ||
One advantage would be that ClientVisitGUID remains the same even when other data is corrected for a John Doe. One disadvantage is that not all our profiles are entered from Cognos, and this field would be blank for those that are not. Collectors can't look the field up in EPR, so it would have to come from Cognos data. | One advantage would be that ClientVisitGUID remains the same even when other data is corrected for a John Doe. One disadvantage is that not all our profiles are entered from Cognos, and this field would be blank for those that are not. Collectors can't look the field up in EPR, so it would have to come from Cognos data. | ||
== Blank CliendVisitGUIDs == | |||
The same scenarios as [[ClientGUID field#Concerns]] could lead to missing lines here. | |||
== Log == | == Log == | ||
* 2022-08-25 - added code to start sending this field to [[Centralized data.mdb]] | |||
* 2021-06-17 - added this field to [[L_Log table]] in [[CCMDB data.mdb]] | |||
Latest revision as of 16:33, 2023 July 13
| Data Element (edit) | |
| Field Name: | ClientVisitGUID |
| CCMDB Label: | N/A |
| CCMDB tab: | not stated |
| Table: | L_Log table |
| Data type: | string |
| Length: | 16 |
| Program: | Med and CC |
| Created/Raw: | Raw |
| Start Date: | 2022-08-29 |
| End Date: | 2300-01-01 |
| Sort Index: | 1.6 |
Unique identifier of a hospital admission for a patient for use with multiple encounters and Cognos data.
The ClientVisitGUID field is the identifier used in Cognos to designate a hospitalization. We collect it to help deal with multiple encounters (eg see also Hospitalization ID, Visit Admit DtTm) and with uniquely matching components of Cognos data to profiles.
One advantage would be that ClientVisitGUID remains the same even when other data is corrected for a John Doe. One disadvantage is that not all our profiles are entered from Cognos, and this field would be blank for those that are not. Collectors can't look the field up in EPR, so it would have to come from Cognos data.
Blank CliendVisitGUIDs
The same scenarios as ClientGUID field#Concerns could lead to missing lines here.
Log
- 2022-08-25 - added code to start sending this field to Centralized data.mdb
- 2021-06-17 - added this field to L_Log table in CCMDB data.mdb