|
|
| (33 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| We use multiple internal numbers to identify patients and patient encoutners. | | We use multiple internal numbers to identify patients and patient encounters. |
| == Serial number ==
| | *[[Serial numbers]] |
| The only number assigned at the data collector level is the '''serial number''', a number assigned manually from a consecutive sequence managed by each individual unit where data is collected. This means the serial number is unique at the unit level, but not across our data.
| | *[[L Person table|L Person]].Person_ID |
| | *[[L Hospitalization]].Hospitalization_ID |
|
| |
|
| === Wrong Serial Numbers === | | == Legacy == |
| Sometimes the wrong serial number gets assigned to a patient. Due to the way HanDBase uses the serial number to relate records in different tables, '''serial numbers can not be changed once a patient has been entered into the PDA'''. If a serial number is changed, some or all of the related records such as diagnoses may go missing.
| | *[[Legacy - Study numbers | Study numbers]] |
| | *[[Index numbers]] |
| | *[[Encounter number]] |
|
| |
|
| If the serial number is a duplicate of an existing or earlier serial, take down the data you entered for that patient on paper, delete the patient, and re-enter the patient with the correct serial number.
| | === batches === |
| | To identify patients sent at the same time (the old concept for this was "batch") see [[L_Log]].SentDtTm |
|
| |
|
| If the serial number has jumped ahead, e.g. you were at serial 900 and accidentally entered 1901 for the next patient, you can continue collecting with that number. You would need to assign further numbers accordingly, i.e. the next patient would be 1902. There will be a gap in your serial numbers, so let Pagasa know so she will not need to confirm with you that this is no error. If you realize the error when you are just starting to enter a patient, it might be easier to start over than to have to communicate about the gap.
| | We used to have |
| | *[[Batch sent number]] |
| | *[[Batch append number]] |
|
| |
|
| == Study Number == | | == Related Articles == |
| A '''study number''' that is unique across the entire dataset is generated when the data is appended to Ed's database. The study number is unique across the entire data set.
| | {{Related Articles}} |
|
| |
|
| == Index Number ==
| |
| " There was some discussion on index # as Julie uses this when compiling data related to the apache score. "
| |
| === Discussion ===
| |
| The above is as per minutes from a meeting... what is the index number, and how is it used?
| |
|
| |
|
| == Encounter Number ==
| | [[Category: Identification numbers]] |
| "Definition of encounter # to be number of admissions to the database of the same patient. "
| | [[Category: Data_Collection_Guide]] |
| === Discussion ===
| | [[Category: Registry Data]] |
| The above is as per minutes from a meeting... what is the encounter number, and how is it used?
| |
| | |
| [[Category:Data_Collection_Guide]] | |
We use multiple internal numbers to identify patients and patient encounters.
Legacy
batches
To identify patients sent at the same time (the old concept for this was "batch") see L_Log.SentDtTm
We used to have
Related Articles