Data dictionary - National Basic Register of Hospital Care (LBZ)
Go back to Database: National Basic Register of Hospital Care (LBZ) (The Netherlands) page
Medical Information[edit | edit source]
Source: Click here to learn more (To access the list, click on "Data model LBZ medical version 9.0" that is available in the section "Data models and source table" of the page).
Table 1: LBZ patient med (contains data from initial treatment of patients in the admission, ambulatory contact, and procedures).
| Variable | Description of the variable |
|---|---|
| AGB setting number | AGB code of the institution |
| Patient ID | Identification of the patient within the institution of care |
| BSN number | Unique patient identification |
| Date of birth | The date the patient was born |
| Sex | The sex of the patient immediately prior to the moment of care |
| Postal Code | The postal code of the Dutch place of residence where the patient is staying immediately prior to the moment of care |
| Country residence | The country where the patient resides immediately prior to the moment of care |
| GP | The patient's general practitioner who is responsible for regular primary care |
| Approved | Patient level alerts are hospital approved |
| Permission to use data | Indication of whether or not the patient agrees with the use of his data for scientific research |
| Patient_id_set | Patient number as used in the institution |
Table 2: LBZ recording (contains the recording data of patients for whom the treatment was performed in the clinic or daycare and ended with discharge of the patient. Concerns all care provided, regardless of whether the nursing day may be claimed).
| Variable | Description of the variable |
|---|---|
| Patient ID | Identification of the patient within the care institution |
| Contact ID | The unique number within the institution under which the moment of care is known |
| Location | Location within the hospital where the admission or outpatient contact took place |
| Case number | The numbers, unique within the institution, under which the patient's care questions are known |
| Type of care | The type of care provided (Clinical, day admission, outpatient contact, observation, or rest) |
| Nature care | The form of care of the care moment |
| Start date | The date on which the relevant moment of care started or took place |
| Start time | The time at which the relevant moment of care started or took place |
| Discharge date | The date on which the recording in question ended |
| Discharge time | The hour at which the recording in question ended |
| Admission specialism | The professional group/specialty of the medical professional who admitted the patient |
| Origin | The residence where the patient was staying immediately prior to the start of the recording |
| Destination | The residence where the patient will stay immediately after the end of the recording |
| Urgency recording | ndication of the urgency of the admission |
| Dismissal specialism | The profession/specialty of the medical professional who discharged the patient |
| Main diagnosis in the moment of care (CvZ80) | The diagnosis that is considered the main reason for admission at the end of the care moment |
| Main diagnosis in the moment of care (ICD-10) | The diagnosis that is considered the main reason for admission at the end of the care moment |
| Main diagnosis in the moment of care diagnosis (thesaurus id) | The diagnosis that is considered the main reason for admission at the end of the care moment |
| Main operation in the moment of care (CvV) | The operation that is considered the most important operation within the admission at the end of the care moment, if any |
| Main operation in the moment of care (CBV) | The operation that is considered the most important operation within the admission at the end of the care moment, if any |
| Main operation in the moment of care (ZA) | The operation that is considered the most important operation within the admission at the end of the care moment, if any |
| Main operation | The transaction that is considered the most important transaction within the recording at the end of the transaction thesaurus care moment, if any |
| Recording specialist | Specialist who admitted the patient |
| Discharge specialist | Specialist who discharged the patient |
| Approved | Admission level alerts are hospital approved |
| Privacy | Level of privacy based on statement signed by the patient on the invoice for the insurer |
| Status | Status of the encoding of the recording |
| Start time incl min | The time in hours and minutes when the relevant moment of care started or took place |
| Dismissal time incl | The time in hours and minutes when the recording in question ended |
Table 3: LBZ diagnosis recording (contains the data of diagnosis that (partly) determined the care provided during the patient's admission).
| Variable | Description of the variable |
|---|---|
| Patient ID | Identification of the patient within the care institution |
| Contact ID | The unique number within the institution under which the moment of care is known |
| Diagnostic ID | Unique number of the diagnosis within the recording |
| Case number | The numbers, unique within the institution, under which the patient's care questions are known |
| Specialty diagnosis | The professional group/specialty of the medical professional to which the patient turns for the treatment of his care request |
| Primary diagnosis indication | Indicates whether the associated diagnosis is the primary diagnosis of admission or ambulatory contact for the specialty in question |
| Diagnosis (CVZ) | Diagnosis that (partly) determined the care provided |
| E/M/C code (CVZ) | Indication of external cause, morphology or complication |
| Diagnosis (ICD-10) | Diagnosis that (partly) determined the care provided |
| MC code (ICD-10) | Indicates the condition that was not present at start of recording |
| Diagnosis (thesaurus id) | Diagnosis that (partly) determined the care provided |
| SNOMED identification | Identification corresponding to SNOMED code |
| Diagnosing specialist | Specialist responsible for the treatment of the care demand |
| Indication of main diagnosis | Indicates whether the relevant diagnosis/specialty combination is the main diagnosis |
| Indication of diagnosis set | Indicates whether that certain diagnoses together form a set |
| Type of practitioner | Indicates whether the diagnosis is linked to a main practitioner, co-practitioner or ICC |
| Approved | Hospital-approved diagnostic-level alerts |
| Indication general secondary diagnosis | Indicates whether the diagnosis applies to all specialisms within the admission as a secondary diagnosis |
| Source | Source in which the diagnosis is recorded |
| AI_proposed_diag | Most probable diagnosis code suggested by algorithm nose |
| AI_certainty_percentage_proposal | Confidence percentage of the proposed diagnosis code by the algorithm |
| diagAI_checked | Indicates whether the medical coder has read the code derived through a AI algorithm has controlled and taken over |
| AI_certainty_percentage_adopted_diagnosis | Confidence percentage of the supplied diagnosis indicated by the algorithm used to derive the code if AI is involved |
| Complication | Indicates if a diagnosis or condition is a complication |
Table 4: LBZ outpatient contact (contains the contact details of patients treated on an outpatient basis that has taken place acutely or by appointment, including telephone contacts or teleconsultations).
| Variable | Description of the variable |
|---|---|
| Patient ID | Identification of the patient within the care institution |
| Contact ID | The unique number within the institution under which the moment of care is known |
| Start date | The date on which the relevant moment of care started or took place |
| Executive specialty | The specialty of the medical professional from the own institution who was responsible for this contact |
| Location | Location within the hospital where the admission or outpatient contact has taken place |
| Case number | The numbers, unique within the institution, under which the patient's care questions are known |
| Nature care | The form of care of the care moment |
| Start time | Time at which the relevant moment of care started or took place |
| CBV transaction | Transaction indicating the type of contact involved |
| Operation ZA | Transaction indicating the type of contact involved |
| Transactions thesaurus id | Transaction indicating the type of contact involved |
| ER | Indicates whether the contact has taken place at the emergency department |
| EAC indication | Indicates whether there is a First Administrative Consultation or First Outpatient Clinic Visit |
| Outpatient clinic number | Outpatient clinic number specified by the hospital |
| Referring specialty | Specialty/profession/service that referred the patient to the hospital for this contact |
| Executive specialist | Medical specialist from own institution who was responsible for this contact |
| Referring specialist | Medical specialist who sees the patient for this contact to the hospital |
| Self referrer | Code of the (self) referrer |
| SEH number | Unique sequence number of ER visit |
| Entry triage code | Triage code upon entry |
| Triage type | Triage system used |
| Triage code | Color code issued at triage |
| Shock room | Indication that indicates whether the shock room has been used |
| Trauma room | Indication that indicates whether the trauma room has been used |
| Date of accident | Date that accident occurred |
| Accident time | Time the accident occurred |
| Reason for visit | Reason for visit to ER |
| Cause injury | Cause of the injury |
| Reference SEH | The person who referred the patient to the ER |
| AGB number referrer SEH | AGB number of the referring institution |
| Transport | Type of transport by which the patient travels to the SEH has arrived |
| Destination after emergency room | Destination of the patient after emergency room visi |
| AGB number destination after ER | AGB number of the institution to which the patient is referred from the emergency department, if not the own institution |
| Time recording ER | Time the patient was admitted to the hospital ER |
| Date Triage | Date that the triage started |
| Triage time | Time that the triage started |
| Date of treatment start | Date the treatment started in the ED |
| Time of treatment start | Time that the treatment in the emergency department has started |
| Date of discharge from Emergency Department | Date on which the treatment of the patient has expired in the emergency department or has died in the emergency department |
| Time discharge ER | Time the patient was discharged from the ER or has died in the ER |
| Date of departure from ER | Date on which the patient physically left the ER |
| Time Departure ER | Time the patient physically leaves the ED |
| Approved | Ambulatory contact level alerts are hospital approved |
| Privacy | Level of privacy based on statement signed by the patient on the invoice for the insurer |
Table 5: LBZ diagnosis outpatient (contains data about diagnosis that (partly) determined the care provided during outpatient care).
| Variable | Description of the variable |
|---|---|
| Patient ID | Identification of the patient within the care institution |
| Contact ID | The unique number within the institution under which the moment of care is known |
| Case number | The numbers, unique within the institution, under which the patient's care questions are known |
| Diagnostic ID | Within the contact unique number of the diagnosis |
| Specialty diagnosis | The professional group/specialty of the medical professional to which the patient turns for the treatment of his care request |
| Diagnosis (CVZ) | Diagnosis that (partly) determined the care provided |
| E/M/C code (CVZ) | Indication of external cause, morphology or complication |
| Diagnosis (ICD-10) | Diagnosis that (partly) determined the care provided |
| MC code (ICD-10) | Indicates complication |
| Diagnosis (thesaurus) | Diagnosis that (partly) determined the care provided |
| SNOMED identification | Identification corresponding to SNOMED code |
| Diagnosing specialist | Specialist responsible for the treatment of the care demand |
| Indication diagnosis set | Indicates that certain diagnoses together form a set |
| Approved | Alerts at the diagnostic ambulatory contact level are hospital-approved |
Table 6: LBZ operation (contains the medical actions performed during or outside admissions and outpatient contacts).
| Variable | Description of the variable |
|---|---|
| Patient ID | Identification of the patient within the care institution |
| Transaction ID | Unique serial number within the institution of the transaction performed |
| Location | Location within the hospital where the admission or outpatient contact took place |
| Case number | The numbers, unique within the institution, under which the patient's care questions are known |
| Requesting specialty | The professional group/speciality of the medical professional who applied |
| Requesting Institution | Institution/practice that requested the transaction |
| Executive specialty | The professional group/specialism of the medical professional who performed the procedure |
| Executing institution | The institution where the transaction was performed if this did not take place in the care institution |
| CVV operation | Operation performed during care |
| CBV transaction | Operation performed during care |
| Operation ZA | Operation performed during care |
| Transactions (thesaurus id) | Operation performed during care |
| Start date | Date on which the procedure started or the date on which the patient entered the OR room |
| Start time | Time on which the procedure started or the date on which the patient entered the OR room |
| End date | Date when the procedure ended or the date when the patient left the OR room |
| End time | Time at which the procedure ended or the time at which the patient left the OR room |
| SNOMED identification | Identification corresponding to SNOMED code |
| Number | Number of times the transaction was executed on the same date |
| Sub trajectory number DIS | Sub trajectory number to which the transaction belongs |
| Typical diagnosis code | DBC typical diagnosis |
| Typical diagnosis (ICD-10) | DBC typical diagnosis |
| Requesting specialist | Medical specialist who requested the operation |
| Performing specialist | Medical specialist who performed the procedure or under whose responsibility the procedure was performed |
| Approved | Procedure level alerts are hospital approved |
| UDI code | Unique identification of the implant according to the GS1 UDI (Barcode) |
| Time implant | start time that implant was implanted or explanted |
Table 7: LBZ medication medical (contains all data on dispensing of medicines carried out in the supplied month - for now only add-on medication and coagulation factors).
| Variable | Description of the variable |
|---|---|
| Number provision | Unique identification of a medicinal product dispensed within a medicinal institution |
| Dispensing date | The date on which the medicine has been supplied to the patient |
| Patient ID | Identification of the patient within the care institution |
| Number of units used | The number of units or fractions of units required to provide the prescribed amount to the patient |
| ZI number | Healthcare identification number of a medicine |
| Indication | Indication for which a drug has been provided to the patient (for add-on and coagulation factors) |
| Medicine code type | Code indicating whether a drug is used as an add-on or coagulation factor |
| Executive specialty | The professional group/specialism of the medical professional who has prescribed the medicine |
| Executive institution (AGB) | Code of the institution where the medicine was prescribed |
| Location | Location within the hospital where the medication was dispensed |
| Approved | Medication level alerts are hospital approved |
| Privacy | Level of privacy based on patient signed statement |
Table 8: LBZ merges (contains information about patient merges to be performed).
| Variable | Description of the variable |
|---|---|
| Patient ID old | Old patient id |
| Patient ID new | New patient ID |
Table 9: LBZ packing slip2 (contains metadata about the medical delivery).
| Variables | Description of variables |
|---|---|
| AGB number | AGB code of the institution |
| Setting sequence numbe | DIS Sequence number of the supplying organizational unit |
| LBZ version number | Version number of the LBZ standard |
| Creation date | Create Date ZIPfile |
| Serial number | Tracking number of the delivery |
| Zip file name | Full name of the ZIP file |
| Software supplier | Name of the software supplier |
| Software package | Name of the software package with which the delivery has been made |
| Software version | Version of the software package |
| Delivery period | Period (calendar month) on which delivery is concerned |
| Indication redelivery | Indicates whether this delivery is a re-delivery |
| Number of Patient | Number of records in file LBZ_patientmed.txt |
| Number of Recording | Number of records in file LBZ_recording.txt |
| Number Diagnosis | Number of records in file LBZ_diagnoseopn.txt |
| Number Outpatient contact | Number of records in file LBZ_outpatient_contact.txt |
| Number Diagnosis outpatient | Number of records in file LBZ_diagnoseamb.txt |
| Number of Operation | Number of records in file LBZ_transaction.txt |
| Number of merges | Number of records in file LBZ-merges.txt |
| Number of medication | Number of records in file medication med.txt |
Financial information[edit | edit source]
Source: Click here to learn more (To access the list, click on "Data model LBZ financial version 24.0" that is available in the section "Data models and source table" of the page).
Table 1: LBZ patientfin (contains all patient data of patients for which a trajectory or procedure or other procedure is submitted).
| Variables | Description of variables |
|---|---|
| AGB number | AGB code of the institution |
| Setting sequence number | DIS Sequence number of the supplying organizational unit |
| Couple number | Unique identification intended to link patient data to a care process, subprocess, medication and/or other procedures |
| Name 1 | The first part of the patient name. Depending on Name Code 1, this is the proper name or the name of the married partner |
| Name prefix 1 | The prefix of first part of patient name |
| Name code 1 | The code that indicates whether Name 1 is own name or partner's name |
| Name 2 | The second part of the patient name. Depending on Name Code 2, this is the proper name or the name of the married partner |
| Name prefix 2 | The prefix of second part of patient name |
| Initials | The patient's initials |
| Postal Code | The postal code of the Dutch place of residence where the patient is staying immediately prior to the start of the sub-route |
| House number | The patient's house number |
| Add house number | The addition of the house number of the patient |
| Country indwelling subtrack | The country where the patient resides immediately prior to the start of the sub-path |
| Date of birth | The date the patient was born |
| Sex | The sex of the patient immediately prior to the start of the subtrack |
| BSN number | Unique patient identification |
| Patient ID | Permanently unique identification of the patient within the institution where the care is provided |
| GP | The patient's general practitioner who is responsible for regular primary care |
| Permission to use data | Indication of whether or not the patient agrees with the use of his data for scientific research |
| Approved | Patient level alerts are hospital approved |
| Patient_id_set | Patient number as used in the institution |
Table 2: LBZ care trajectory (contains data about all care processes with a start date in the supplied month).
| Variables | Description |
|---|---|
| Care pathway number | Unique identification of the care process within the institution where the care is provided |
| Care pathway number parent | Reference to another Care Pathway, being the main Care Pathway |
| Start date of care process | The date on which the care process started |
| End date care process | The date on which the care process ended |
| Couple number | Unique identification intended to link patient data to a care process, sub-process, medication and/or other procedures |
| Reference setting AGB | Unique identification of the institution that referred the patient |
| Referring specialty | Specialism/profession/service that has referred the patient for this care process |
| Code (self) referrer | Code of the (self) referrer |
| Care pathway number Referring specialty | The care trajectory where the treating specialism has referred to this care trajectory |
| Approved | Admission level alerts are hospital approved |
Table 3: LBZ declaration dataset (contains the data about declaration sets).
| Variables | Description |
|---|---|
| Declaration dataset number | Unique identification of the set of associated data with regard to 1 declarable |
| Hashtotal DIS | Hash as derived for DIS |
| Hashversion DIS | Hash version used |
| Certificate version hash | Certificate to decrypt hashtota |
| Tableset version | Version of the tableset |
| Grouper version | Version of the Grouper |
| Status set | Status indicating whether the declaration dataset determined numerically in the grouper for the purpose of declaration whether it still has a provisional number |
Table 4: LBZ sub trajectory (contains the data about the sub-trajectories opened in the supplied month).
| Variables | Description |
|---|---|
| Declaration dataset number | Unique identification of the set of related data with regard to 1 declarable sub-process and related care processes |
| Care pathway number | Unique identification of the care process within the institution where the care is provided |
| Subtrack number | Unique identification of the sub-track for each institution and organizational unit |
| Main trajectory indication | Indication that indicates whether this sub-route is a main route |
| Sub-project start date | The date on which the relevant subjourney started |
| End date sub-project | The date on which the relevant subjourney was terminated |
| Treatment specialty | The professional group/specialism of the medical professional to which the patient turns for the treatment of his care request |
| Care type | DBC care type |
| Care question | DBC care question |
| Typical diagnosis code | DBC typical diagnosis |
| DBC hospital costs | Integral costs |
| Fee total | Total fee that has been invoiced |
| Care product | DBC Care product |
| Declaration | Declaration code |
| Closing reason | Reason for closing DBC |
| Age | Age at the start date of sub-process |
| Claim_ZVW | Reimbursement at the expense of ZVW |
| Entitlement_ZVWapplied | Indication that indicates whether the ZVW entitlement code has been used |
| ZA authorization in profile | Indication that indicates whether there is permission in the profile |
| Orange ZA | Indication that indicates whether orange care activities are involved |
| Care activity translation applied | Indication that indicates whether there is an undelivered activity for which a conversion table has been used |
| Setting reserved 1 | Reserved position for Y/N indication. At this point, only a space is expected |
| Setting reserved 2 | Reserved position for Y/N indication. At this point, only a space is expected |
| Setting reserved 3 | Reserved position for Y/N indication. At this point, only a space is expected |
| UZOVI number | Health insurer of the patient to whom the billable products have been or will be invoiced |
| Typical diagnosis ICD-10 | DBC typical diagnosis in ICD-10 coding |
| 1st supplement ICD-10 | First additional ICD-10 diagnosis (set of typical diagnosis ICD10 and additions describe the diagnosis e.g. in case of dagger and asterisk combinations or in case of syndromes) |
| 2nd supplement ICD-10 | Second additional ICD-10 diagnosis (set of typical diagnosis ICD10 and additions describe the diagnosis e.g. in case of dagger and asterisk combinations or in case of syndromes) |
| 3rd supplement ICD-10 | Third additional ICD-10 diagnosis (set of typical diagnosis ICD10 and additions describe the diagnosis e.g. in case of dagger and asterisk combinations or in case of syndromes) |
| 4th supplement ICD-10 | Fourth additional ICD-10 diagnosis (set of typical diagnosis ICD10 and additions describe the diagnosis e.g. in case of dagger and asterisk combinations or in case of syndromes) |
| Declaration date | Date on which the claim was submitted to the insurer or another body (or the patient). |
| Handling subspecialty code | Specialism code supplemented with the subspecialty of the medical professional who is responsible for the subprocess |
| Treating subspecialty internal code | Internal code for treating ecternal (sub)specialism |
| Last invoice date | Last date on which an invoice for this sub-track was sent |
| Balance billed charges | The net invoiced costs at the time of sending the last invoice |
| Balance invoiced fee | The net invoiced fee at the time of sending the last invoice |
| Reason for failure | Reason for failure in the grouper |
| Approved | Admission level alerts are hospital approved |
| Couple number | Unique identification intended to link patient data to a care process, subprocess, medication and/or other procedures |
| Diagnostic thesaurus id | Id diagnosis thesaurus of DBC typical diagnosis |
| Privacy | Level of privacy based on statement signed by the patient on the invoice for the insurer |
Table 5: LBZ additional diagnosis (contains diagnoses that have influenced the treatment with regard to the relevant subpath).
| Variable | Description |
|---|---|
| Subtrack number | Unique identification of the sub-track for each institution and organizational unit |
| Specialty diagnosis | The specialty of the medical professional who made the diagnosis |
| Diagnosis code DBC | Diagnosis in terms of DBC code |
| Diagnosis ICD-10 | Diagnosis in terms of ICD-10 |
| Diagnostic thesaurus id | Id diagnosis thesaurus of DBC typical diagnosis |
| Approved | Admission level alerts are hospital approved |
Table 6: LBZ supplied care profile (contain all care activities performed in the context of diagnosis, treatment, consultations, nursing days and/or (expensive) medicines, which are linked to a sub-process).
| Variables | Description |
|---|---|
| Declaration dataset number | Number of the dataset to which this care profile belongs |
| Care activity number | Unique serial number of the care activity performed within the institution |
| Subtrack number | Unique identification of the sub-track for each institution and organizational unit |
| Requesting specialty | Specialism code of the requesting specialism |
| Applicant institution | Institution/practice that requested the care activity |
| Executive specialty | The specialty of the medical professional who performed the care activity |
| Executive setting | The hospital where the care activity was performed if this did not take place in the hospital of care |
| Care activity code | Care activity code of the performed care activity |
| Date of care activity | The date on which the implementation of the care activity started |
| Declaration code | Declaration code |
| Number | Number of times the care activity within the subtrack was performed |
| Sales price hospital | The declared sales price per unit/integral rate |
| Sales price fee | The declared sales price fee per unit |
| UZOVI number | Health insurer of the patient to whom the billable products have been or will be invoiced |
| Code CBV | CBV code of the care activity performed |
| Addon Information | Detail information about the transaction |
| Declaration date | Date of submission of declaration |
| Recording number | The unique number within the institution under which the clinical admission or day treatment is known |
| Internal registration code | Internal code for care activity/transaction at hospital |
| AVtype | Applicant type |
| Requesting subspecialty code | Subspecialty code of the requesting specialism |
| Requesting subspecialty code intern | Internal code for the requesting (sub) specialism |
| Executive subspecialty code | Subspecialty code of the performing specialism |
| Executive subspecialty code internal | Internal code for executive (sub) specialism |
| Producing Department | Department where the transaction was performed |
| Approved | Admission level alerts are hospital approved |
| Transactions Thesaurus ID | Operation performed during care |
| Location | Location within the hospital where the care activity took place |
Table 7: LBZ fee (contains the fees of treating and supporting specialisms for DBC trajectories).
| Variable | Description |
|---|---|
| Subtrack number | Unique identification of the sub-track for each institution and organizational unit |
| Specialism Code | Code of the treating or supporting specialty |
| Cost category | Cost type associated with fee |
| Fee | Fee of the treating or supporting specialty |
| Approved | Admission level alerts are hospital approved |
Table 8: LBZ other transaction (contain transactions that cannot (yet) be linked to a sub-project).
| Variable | Description |
|---|---|
| Transaction number | Unique serial number within the institution of the transaction performed |
| Couple number | Unique identification intended to link patient data to a care process, subprocess, medication and/or other procedures |
| Requesting specialty | Specialism code of the requesting specialism |
| Applicant institution | Institution/practice that requested the transaction |
| Executive specialty | The specialty of the medical professional from the own institution who performed the procedure |
| Executive setting | The institution where the transaction was performed if this was not done in the institution of care |
| Care activity code | Care activity code of the performed care activity |
| Declaration code | Declaration code |
| Date transaction | The date on which the execution of the transaction started |
| Sales price hospital | The declared sales price per unit/integral amount |
| Sales price fee | The declared sales price fee per unit |
| Number | Number of times the transaction was
performed |
| UZOVI number | Health insurer of the patient to whom the billable products have been or will be invoiced |
| Code CBV | CBV code of the transaction performed |
| Addon information | Additional information about the transaction |
| Declaration date | submission date |
| Recording number | The unique number within the institution under which the clinical admission or day treatment is known |
| Internal registration code | Internal code for care activity/transaction at hospital |
| AVtype | applicant type |
| Requesting subspecialty code | Subspecialty code of the requesting specialism |
| Requesting subspecialty code intern | Internal code for the requesting (sub) specialism |
| Executive subspecialty code | Subspecialty code of the performing specialism |
| Executive subspecialty code internal | Internal code for executive (sub) specialism |
| Producing Department | Department where the transaction was performed |
| Approved | Admission level alerts are hospital approved |
| Transactions thesaurus id | Operation performed during care |
| Location | Location within the hospital where the care activity took place |
Table 9: LBZ medication financial (contains all data on dispensing of medicines per patient carried out in the supplied month - only addon medication and coagulation factors).
| Variable | Description |
|---|---|
| Medicine dispensing number | Unique identification of a medicinal product dispensed within an institution |
| Issue date | The date the drug was dispensed or na administered to the patient |
| Care pathway number | Unique identification of the care process within the institution where the care is provided |
| Couple number | Unique identification intended to link patient data to a care process, subprocess, medication and/or other procedures |
| Number of units used | the number of units or fractions of units required to provide the prescribed amount to the patient |
| ZI number | Z-index number of a drug Numeric |
| Indication | Indication for which a drug has been provided to the patient (for add-on and coagulation factors) |
| Drug type code | Code indicating whether a drug is used as an add-on or coagulation factor |
| Declared amount | The declared amount of the add-on drug or coagulation factor |
| Executive specialty | The professional group/specialty of the medical professional who has prescribed the medicine |
| Executive institution | AGB code of the institution where the medicine is prescribed |
| Declaration date | Submission date |
| Executive subspecialty code | Subspecialty code of the performing specialty |
| Executive subspecialty code internal | Internal code for executive (sub) specialty |
| Producing Department | Department where the transaction was performed |
| Uzovi number | Health insurer of the patient to whom the billable products have been or will be invoiced |
| Location | Location within the hospital where the drug is prescribed |
| Approved | Medication level alerts are hospital approved |
| Privacy | Level of privacy based on statement signed by the patient on the invoice for the insurer |
Table 10: LBZ packing slip1 (contains metadata about the delivery of the financial data stream).
| Variable | Description |
|---|---|
| Setting number AGB | Unique identification of the institution that provided care to the patient according to AGB code list |
| Setting Sequence No. DIS | Sequence number of the supplying organizational unit |
| LBZ version number | Version number of the LBZ standard |
| Creation date | Create Date ZIPfile |
| Serial number | Tracking number of the delivery |
| zip file name | Full name of the ZIP file |
| Software supplier | Name of the software vendor |
| Software package | Name of the software package with which the delivery was made |
| Software version | Version of the software package |
| Delivery period | Period (calendar month) to which the delivery relates |
| Re-delivery indication | Indication indicating whether this delivery is a re-delivery |
| Number of Patient | Number of records in file LBZ_patient_S1.txt |
| Number of care pathway | Number of records in file care trajectory.txt |
| Number of declaration dataset | Number of records in declarationdataset.txt file |
| Number of subtrack | Number of records in file subtraject.txt Numeric |
| Number of fees | Number of records in file fee.txt |
| Number of care profile | Number of records in file supplied care profile.txt |
| Number of secondary diagnosis | Number of records in file secondary diagnosis.txt |
| Number of other transactions | Number of records in file other transaction.txt |
| Number of medication fin | Number of records in the medicationfin.txt |
| User name | User name |
| Chamber of Commerce number | Chamber of Commerce numberunder which the institution is registered |