Gms dict v1_1

443 views
379 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
443
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Gms dict v1_1

  1. 1. GENERAL MEDICAL SUBSIDY DATAMART DATA DICTIONARY Version 1.1 October 2003
  2. 2. General Medical Subsidy Datamart Data Dictionary Front PagesReproduction of materialThe New Zealand Health Information Service (NZHIS) permits the reproduction of material from thispublication without prior notification, providing all the following conditions are met: the information mustnot be used for commercial gain, must not be distorted or changed, and NZHIS must be acknowledgedas the source.DisclaimerThe Ministry of Health gives no indemnity as to the correctness of the information or data supplied. TheMinistry of Health shall not be liable for any loss or damage arising directly or indirectly from the supplyof this publication.All care has been taken in the preparation of this publication. The data presented was deemed to beaccurate at the time of publication, but may be subject to change. It is advisable to check for updates tothis publication via NZHIS’s web site at http://www.nzhis.govt.nz.New Zealand Health Information ServiceThe New Zealand Health Information Service (NZHIS) is a group within the Ministry of Healthresponsible for the collection and dissemination of health-related data. NZHIS has as its foundation thegoal of making accurate information readily available and accessible in a timely manner throughout thehealth sector. The vision of NZHIS is to be recognised as a leader in the provision of health informationservices, and to support the health sector’s ongoing effort to improve the health status of NewZealanders.Reporting environmentsReporting environments such as Business Objects and data extracts will not necessarily contain all datadescribed in this Data Dictionary.PublicationsA complete list of NZHIS’s publications is available from New Zealand Health Information Service, POBox 5013, Wellington, or via NZHIS’s web site at http://www.nzhis.govt.nz.Any enquiries about or comments on this publication should be directed to:The Publications OfficerNew Zealand Health Information ServicePO Box 5013,Wellington.Phone: (04) 922 1800 Fax: (04) 922-1899Email: nzhis-pub@nzhis.govt.nzPublished by New Zealand Health Information Service© 2003, New Zealand Health Information ServiceVersion: 1.1 NZHISOctober 2003
  3. 3. General Medical Subsidy Datamart Data Dictionary Front PagesIntroductionObjectives The objectives of the New Zealand Health Information Service (NZHIS) Data Dictionaries are to: • describe the information available within the National Collections • promote uniformity, availability and consistency across the National Collections • support the use of nationally agreed protocols and standards wherever possible • promote national standard definitions and make them available to users. It is hoped that the greater level of detail along with clear definitions of the business rules around each element will assist with providing and using the data.Audiences The target audiences for NZHIS Data Dictionaries are data providers, software developers, and data users.New format All data element definitions in the NZHIS Data Dictionaries are presented in a format based on the Australian Institute of Health and Welfare National Health Data Dictionary. This dictionary is based on the ISO/IEC Standard 11179 Specification and Standardization of Data Elements—the international standard for defining data elements issued by the International Organization for Standardization and the International Electrotechnical Commission. The format is described in detail in Appendix A of this dictionary.Changes to dictionary format A more rigorous approach to recording changes in the data elements has been introduced in these dictionaries along with background material on the features of time-series data for each element. In summary, the changes to the data dictionaries include: • standardisation of the element names so that, for instance, a healthcare user’s NHI number is referred to as NHI number in all collections • elements are listed alphabetically within each table, and the tables are organised alphabetically • each table is described • verification rules, historical information, and data quality information are included • alternative names for the elements are listed • information about how the data is collected is given • related data, and references to source documents and source organisations are included • an alphabetical index is included • code tables are included with the element, or a reference given to the NZHIS web site (for large or dynamic code tables).Version: 1.1 NZHISOctober 2003
  4. 4. General Medical Subsidy Datamart Data Dictionary Front PagesTable of ContentsGeneral Medical Subsidy Datamart (GMS)..................................................................................summaryAge Band table .............................................................................................................................................. 1 Age in years................................................................................................................................................. 1 Five year band............................................................................................................................................. 2 Ten year band ............................................................................................................................................. 3Claim Code table ........................................................................................................................................... 4 Claim code................................................................................................................................................... 4 CSC Flag ..................................................................................................................................................... 5 Description................................................................................................................................................... 6 HUHC Flag .................................................................................................................................................. 7 Patient category .......................................................................................................................................... 8Claim Received Date table........................................................................................................................... 9Contract Details table ................................................................................................................................. 10 Allow payment ........................................................................................................................................... 10 Contract description .................................................................................................................................. 11 Contract expiry date.................................................................................................................................. 12 Contract number ....................................................................................................................................... 13 Contract type ............................................................................................................................................. 14 Current version.......................................................................................................................................... 15 DHB SSSG ................................................................................................................................................ 16 Payment days............................................................................................................................................ 17 Payment term code................................................................................................................................... 18 Perorg ID ................................................................................................................................................... 19DHB Reference table .................................................................................................................................. 20 DHB code .................................................................................................................................................. 20 DHB ID....................................................................................................................................................... 22 DHB name ................................................................................................................................................. 23 DHB SSSG ................................................................................................................................................ 24Global Time table ........................................................................................................................................ 25 Calendar month number ........................................................................................................................... 25 Calendar quarter ....................................................................................................................................... 26 Calendar quarter number ......................................................................................................................... 27 Calendar year............................................................................................................................................ 28 Calendar year and month ......................................................................................................................... 29 Day of month ............................................................................................................................................. 30 Day of week............................................................................................................................................... 31 Financial month number ........................................................................................................................... 32 Financial quarter ....................................................................................................................................... 33 Financial quarter number.......................................................................................................................... 34 Financial year ............................................................................................................................................ 35 Month ......................................................................................................................................................... 36 SQL date.................................................................................................................................................... 37GMS Health Event table ............................................................................................................................. 38 Amount claimed (excl GST)...................................................................................................................... 38 Amount paid (excl GST) ........................................................................................................................... 39 Invoice number.......................................................................................................................................... 40 Locum flag ................................................................................................................................................. 41 Original item ID.......................................................................................................................................... 42 Original message ID ................................................................................................................................. 43 Original transaction ID .............................................................................................................................. 44Healthcare User table ................................................................................................................................. 45 Date of birth ............................................................................................................................................... 45 Date of death............................................................................................................................................. 46 Deprivation Index ...................................................................................................................................... 47 DHB code .................................................................................................................................................. 48 DHB name ................................................................................................................................................. 49 Domicile code............................................................................................................................................ 50 Domicile name........................................................................................................................................... 51Version: 1.1 NZHISOctober 2003
  5. 5. General Medical Subsidy Datamart Data Dictionary Front Pages Encrypted NHI number ............................................................................................................................. 52 Ethnicity code 1......................................................................................................................................... 54 Ethnicity code 2......................................................................................................................................... 56 Ethnicity code 3......................................................................................................................................... 57 Ethnicity description .................................................................................................................................. 58 HHS code .................................................................................................................................................. 59 HHS name ................................................................................................................................................. 60 Inner group ................................................................................................................................................ 61 Inner group description ............................................................................................................................. 62 Locality code ............................................................................................................................................. 63 Locality name ............................................................................................................................................ 64 Master encrypted NHI number ................................................................................................................. 65 Outer group ............................................................................................................................................... 67 Outer group description ............................................................................................................................ 68 Prioritised ethnic code .............................................................................................................................. 69 Region name ............................................................................................................................................. 70 RHA code .................................................................................................................................................. 71 Sex............................................................................................................................................................. 72 Sub-locality code....................................................................................................................................... 73 Sub-locality name...................................................................................................................................... 75 Territorial Authority.................................................................................................................................... 76 Territorial Authority code........................................................................................................................... 77Payee table................................................................................................................................................... 78 Payee description...................................................................................................................................... 78 Payee DHB................................................................................................................................................ 79 Payee number ........................................................................................................................................... 80 Payee perorg number ............................................................................................................................... 81 Perorg legal name..................................................................................................................................... 82 Perorg name.............................................................................................................................................. 83 Sequence number..................................................................................................................................... 84Payment Date table..................................................................................................................................... 85Provider table .............................................................................................................................................. 86 Current practising certificate..................................................................................................................... 86 Deregistration date.................................................................................................................................... 87 Health professional group code ............................................................................................................... 88 Perorg name.............................................................................................................................................. 89 Perorg number .......................................................................................................................................... 90 Pharmac provider type.............................................................................................................................. 91 Pharmac registration number ................................................................................................................... 92 Provider address ....................................................................................................................................... 93 Provider address 2.................................................................................................................................... 94 Provider occupation .................................................................................................................................. 95 Provider registration number .................................................................................................................... 96 Provider type ............................................................................................................................................. 97Visit Date table............................................................................................................................................. 98Appendix A: Data Dictionary Template .......................................................................................................iAppendix B: Glossary ................................................................................................................................. iiiAppendix C: Logical Groups of Elements................................................................................................ ivAppendix D: Code Table Index ....................................................................................................................vAppendix E: Alphabetical Index of Data Elements ................................................................................. viVersion: 1.1 NZHISOctober 2003
  6. 6. General Medical Subsidy Datamart Data Dictionary Front PagesGeneral Medical Subsidy Datamart (GMS)Scope Purpose The General Medical Subsidy Data Warehouse (GMS) is used by Ministry of Health analysts and DHBs to: • monitor contracts with providers • support forecasting and setting of annual budgets • analyse health needs and assess policy effectiveness. Content GMS Datamart contains the fee-for-service payments made to doctors for patient visits that have been processed by the HealthPAC Proclaim system.Start date GMS Datamart was established in August 2003 and contains data from November 2001.Guide for use All data transferred from HealthPAC to the GMS Datamart is claim- related data sent by claimants. Definitions in the GMS Datamart Data Dictionary are based on the GP Section 88 Notice. The GMS Datamart only includes health events processed by HealthPAC. Most health events for which there are no fee claims are not included in the GMS Datamart.Contact information For further information about this collection or to request specific datasets or reports, contact the NZHIS Analytical Services team on ph 04 922 1800, fax 04 922 1897, or e-mail inquiries@nzhis.govt.nz, or visit the NZHIS web site www.nzhis.govt.nz.Collection methods – guide for All transactional data is sourced from HealthPAC’s Proclaimproviders system. It is loaded into the GMS Datamart via an intermediate data store (the IDS).Frequency of updates The GMS Datamart receives monthly extracts from HealthPAC via the IDS.Security of data The GMS Datamart is accessed by authorised NZHIS staff for maintenance, data quality, audit and analytical purposes. Authorised members of the Ministry of Health and DHBs have access to the data for analytical purposes, via the Business Objects reporting tool and the secure Health Information Network (HIN). Business Objects contains a subset of the data described in the Data Dictionary.Version: 1.1 NZHISOctober 2003
  7. 7. General Medical Subsidy Datamart Data Dictionary Front PagesPrivacy issues The Ministry of Health is required to ensure that the release of information recognises any legislation related to the privacy of health information, in particular the Official Information Act 1982, the Privacy Act 1993 and the Health Information Privacy Code 1994. Information available to the general public is of a statistical and non-identifiable nature. Researchers requiring identifiable data will usually need approval from an Ethics Committee. As at August 2003, the encrypted NHI number is stored for approximately 85 percent of records.National reports and NZHIS releases monthly reports to the DHBs on the HIN in MSpublications Excel format.Data provision Customised datasets or summary reports are available on request, either electronically or on paper. Staff from the NZHIS Analytical Services team can help to define the specifications for a request and are familiar with the strengths and weaknesses of the data. The NZHIS Analytical Services team also offers a peer review service to ensure that NZHIS data is reported appropriately when published by other organisations. There may be charges associated with data extracts.Version: 1.1 NZHISOctober 2003
  8. 8. GMS Datamart Data Dictionary Age Band tableAge Band tableTable name: Age Band tableName in database: dim_age_band Version: 1.0 Version date: 31-Jul-2003Definition: This reference table contains a record for each year from 0 to 115, grouped into 5 and 10 year age bands.Guide for Use:Primary Key:Business Key:Relational Rules:Age in yearsAdministrative statusReference ID: Version: 1.0 Version date: 31-Jul-2003Identifying and defining attributesName: Age in yearsName in database: age_in_yearsOther names:Element type: Data elementDefinition: The age of the healthcare user.Context:Relational and representational attributesData type: number Field size: 3 Layout: NNNData domain: 0 to 115Guide for use: 0 is used for those less than one year old.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 1October 2003
  9. 9. GMS Datamart Data Dictionary Age Band tableFive year bandAdministrative statusReference ID: Version: 1.0 Version date: 31-Jul-2003Identifying and defining attributesName: Five year bandName in database: five_year_bandOther names:Element type: Data elementDefinition: A five year range of ages, eg, 6 to 10.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: NNN to NNNData domain:Guide for use: Note: The first band (0 to 5) is 6 years.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 2October 2003
  10. 10. GMS Datamart Data Dictionary Age Band tableTen year bandAdministrative statusReference ID: Version: 1.0 Version date: 31-Jul-2003Identifying and defining attributesName: Ten year bandName in database: ten_year_bandOther names:Element type: Data elementDefinition: A ten year range of ages, eg, 11 to 20.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: NNN to NNNData domain:Guide for use: Note: The first band (0 to 10) is 11 years.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 3October 2003
  11. 11. GMS Datamart Data Dictionary Claim Code tableClaim Code tableTable name: Claim Code tableName in database: dim_claim_code Version: 1.0 Version date: 31-Jul-2003Definition: This reference table contains codes that describe the patients subsidy status at the time of the event.Guide for Use:Primary Key:Business Key:Relational Rules:Claim codeAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Claim codeName in database: claim_codeOther names:Element type: Composite data elementDefinition: A code describing the age group of the patient and whether they have a High Use Health Card and/or a Community Services Card.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: ANData domain: The first character is the patient category of A (Adult), Y (Youth) or J (Junior). The second is 1 (CSC use), 3 (no card presented) or Z (HUHC use).Guide for use: Claim code must be consistent with Patient category, CSC flag, and HUHC flag. A also applied to healthcare users who are aged between 16 and 18, and are financially independent and/or married.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 4October 2003
  12. 12. GMS Datamart Data Dictionary Claim Code tableCSC FlagAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: CSC FlagName in database: csc_flagOther names:Element type: Data elementDefinition: Indicates whether the patient is a Community Services Card holder.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: AData domain: Y Community Services Card used by healthcare user N Community Services Card not used by healthcare userGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 5October 2003
  13. 13. GMS Datamart Data Dictionary Claim Code tableDescriptionAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DescriptionName in database: descriptionOther names:Element type: Data elementDefinition: A text description of the claim code.Context:Relational and representational attributesData type: varchar Field size: 64 Layout:Data domain:Guide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 6October 2003
  14. 14. GMS Datamart Data Dictionary Claim Code tableHUHC FlagAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: HUHC FlagName in database: huhc_flagOther names:Element type: Data elementDefinition: Indicates whether the patient used a High Use Health Card.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: AData domain: Y High Use Health Card used by healthcare user N High Use Health Card not used by healthcare userGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 7October 2003
  15. 15. GMS Datamart Data Dictionary Claim Code tablePatient categoryAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Patient categoryName in database: patient_categoryOther names:Element type: Data elementDefinition: A code indicating the age group of the healthcare user.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: AData domain: A Adult 18 and above J Juvenile 6 – 17 years Y Child under 6 years G GMV motor vehicle subsidyGuide for use: Part of the claim code. A also applies to healthcare users who are aged between 16 and 18, and are financially independent and/or married.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 8October 2003
  16. 16. GMS Datamart Data Dictionary Claim Received Date tableClaim Received Date tableTable name: Claim Received Date tableName in database: dim_claim_received_date Version: 1.0 Version date: 31-Jul-2003Definition: This is a view of the Global Time table, which contains a record for every day between 1900 and 2050, with descriptive attributes for each day.Guide for Use: Used as a reference table for the date when the claim was received by HealthPAC. Static table.Primary Key:Business Key:Relational Rules:Version: 1.1 NZHIS Page 9October 2003
  17. 17. GMS Datamart Data Dictionary Contract Details tableContract Details tableTable name: Contract Details tableName in database: dim_contract_details Version: 1.0 Version date: 31-Jul-2003Definition: This reference table contains a list of contract numbers and descriptions.Guide for Use: All current contracts should be contained in the table. Any missing (historical) contracts are automatically added if referenced by a transaction, although this is limited to contract number, description and version. Updated each month.Primary Key:Business Key:Relational Rules:Allow paymentAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Allow paymentName in database: allow_paymentOther names:Element type: Data elementDefinition: A flag indicating whether services claimed under the contract are payable or not.Context:Relational and representational attributesData type: char Field size: 1 Layout: AData domain: Y Payment allowed N Payment not allowedGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 10October 2003
  18. 18. GMS Datamart Data Dictionary Contract Details tableContract descriptionAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Contract descriptionName in database: contract_descriptionOther names:Element type: Data elementDefinition: A free-text description of the contract.Context:Relational and representational attributesData type: varchar Field size: 80 Layout:Data domain:Guide for use: Contains, for example, type of services, dates.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 11October 2003
  19. 19. GMS Datamart Data Dictionary Contract Details tableContract expiry dateAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Contract expiry dateName in database: contract_expiry_dateOther names:Element type: Data elementDefinition: The end date on a given contract or the termination date on a contract.Context:Relational and representational attributesData type: datetime Field size: Layout:Data domain:Guide for use: If there is an end date and a termination date in HealthPACs Contract and Monitoring System, the earlier date is extracted as the Contract expiry date.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 12October 2003
  20. 20. GMS Datamart Data Dictionary Contract Details tableContract numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Contract numberName in database: contract_numberOther names:Element type: Data elementDefinition: The number of the contract that was the basis for the funding of the service provided.Context:Relational and representational attributesData type: varchar Field size: 11 Layout:Data domain:Guide for use: This is the business key for the Contract Details table.Verification rules: HealthPAC-generated number.Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 13October 2003
  21. 21. GMS Datamart Data Dictionary Contract Details tableContract typeAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Contract typeName in database: contract_typeOther names:Element type: Data elementDefinition: The type of contract, eg, a section 51 notice.Context:Relational and representational attributesData type: varchar Field size: 10 Layout:Data domain:Guide for use: Not used.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 14October 2003
  22. 22. GMS Datamart Data Dictionary Contract Details tableCurrent versionAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Current versionName in database: current_versionOther names:Element type: Data elementDefinition: The version number of the contract.Context:Relational and representational attributesData type: varchar Field size: 2 Layout:Data domain:Guide for use: Not used.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 15October 2003
  23. 23. GMS Datamart Data Dictionary Contract Details tableDHB SSSGAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB SSSGName in database: dhbOther names:Element type: Data elementDefinition: District Health Board code allocated by Shared Support Services Group.Context: Represents the District Health Board responsible for funding the services under the contract.Relational and representational attributesData type: varchar Field size: 3 Layout: AAAData domain: NLD Northland NWA Waitemata CAK Auckland SAK Counties Manukau WKO Waikato LKS Lakes BOP Bay of Plenty TRW Tairawhiti TKI Taranaki HWB Hawkes Bay WNI Whanganui MWU MidCentral HUT Hutt CAP Capital and Coast WRP Wairarapa NLM Nelson Marlborough WCO West Coast CTY Canterbury SCY South Canterbury OTA Otago SLD Southland MOH Ministry of Health OVS OverseasGuide for use: HealthPAC DHB codes. For completeness, the DHB SSSG code includes the Ministry of Health. Not used.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 16October 2003
  24. 24. GMS Datamart Data Dictionary Contract Details tablePayment daysAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Payment daysName in database: payment_daysOther names:Element type: Data elementDefinition: The number of days within which the provider is to be paid for On Demand payments.Context:Relational and representational attributesData type: number Field size: Layout:Data domain:Guide for use: Working days only, ie, excluding weekends and national public holidays. Not used.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 17October 2003
  25. 25. GMS Datamart Data Dictionary Contract Details tablePayment term codeAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Payment term codeName in database: payment_term_codeOther names:Element type: Data elementDefinition: The terms of payment for the contract.Context:Relational and representational attributesData type: varchar Field size: 10 Layout:Data domain: 1mont 2mont 3mont 2week 6mont 1off noneGuide for use: Not used.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 18October 2003
  26. 26. GMS Datamart Data Dictionary Contract Details tablePerorg IDAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Perorg IDName in database: perorg_idOther names:Element type: Data elementDefinition: The unique identifier for the person or organisation that receives payment for the work done under the contract.Context:Relational and representational attributesData type: number Field size: Layout:Data domain:Guide for use: Perorg is person or organisation. In the GMS Datamart, perorgs are restricted to providers and organisations that hold a contract.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 19October 2003
  27. 27. GMS Datamart Data Dictionary DHB Reference tableDHB Reference tableTable name: DHB Reference tableName in database: dim_dhb_reference Version: 1.0 Version date: 31-Jul-2003Definition: This reference table contains a list of DHB codes and names.Guide for Use: There is also an entry for the Ministry of Health.Primary Key:Business Key:Relational Rules:DHB codeAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB codeName in database: dhb_codeOther names:Element type: Data elementDefinition: District Health Board code as defined by the Senior Advisor, DHB Services, Ministry of Health.Context:Relational and representational attributesData type: char Field size: 3 Layout: NNNData domain: 011 Northland 021 Waitemata 022 Auckland 023 Counties Manukau 031 Waikato 042 Lakes 047 Bay of Plenty 051 Tairawhiti 061 Hawkes Bay 071 Taranaki 081 MidCentral 082 Whanganui 091 Capital and Coast 092 Hutt 093 Wairarapa 101 Nelson Marlborough 111 West Coast 121 Canterbury 123 South Canterbury 131 Otago 141 Southland 999 OverseasGuide for use: May contain leading zeroes. Derived from NZHIS geocoding of the claimant address.Verification rules:Collection method:Related data:Version: 1.1 NZHIS Page 20October 2003
  28. 28. GMS Datamart Data Dictionary DHB Reference tableAdministrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 21October 2003
  29. 29. GMS Datamart Data Dictionary DHB Reference tableDHB IDAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB IDName in database: dhb_idOther names:Element type: Data elementDefinition: Statistics NZ code for District Health Boards.Context:Relational and representational attributesData type: number Field size: 2 Layout: NNData domain: 1 Northland 2 Waitemata 3 Auckland 4 Counties Manukau 5 Waikato 6 Lakes 7 Bay of Plenty 8 Tairawhiti 9 Taranaki 10 Hawkes Bay 11 Whanganui 12 MidCentral 13 Hutt 14 Capital and Coast 15 Wairarapa 16 Nelson Marlborough 17 West Coast 18 Canterbury 19 South Canterbury 20 Otago 21 Southland 99 OverseasGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation: Statistics NZVersion: 1.1 NZHIS Page 22October 2003
  30. 30. GMS Datamart Data Dictionary DHB Reference tableDHB nameAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB nameName in database: dhb_nameOther names:Element type: Data elementDefinition: Legal name of the District Health Board.Context: The DHB that paid for the service.Relational and representational attributesData type: varchar Field size: 40 Layout: Free textData domain:Guide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 23October 2003
  31. 31. GMS Datamart Data Dictionary DHB Reference tableDHB SSSGAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB SSSGName in database: dhb_ssgOther names:Element type: Data elementDefinition: District Health Board code allocated by Shared Support Services Group.Context:Relational and representational attributesData type: char Field size: 3 Layout: AAAData domain: NLD Northland NWA Waitemata CAK Auckland SAK Counties Manukau WKO Waikato LKS Lakes BOP Bay of Plenty TRW Tairawhiti TKI Taranaki HWB Hawkes Bay WNI Whanganui MWU MidCentral HUT Hutt CAP Capital and Coast WRP Wairarapa NLM Nelson Marlborough WCO West Coast CTY Canterbury SCY South Canterbury OTA Otago SLD Southland MOH Ministry of Health OVS OverseasGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 24October 2003
  32. 32. GMS Datamart Data Dictionary Global Time tableGlobal Time tableTable name: Global Time tableName in database: Version: 1.0 Version date: 31-Jul-2003Definition: Contains a record for every day between 1900 and 2050, with descriptive attributes for each day.Guide for Use: Static table.Primary Key:Business Key:Relational Rules:Calendar month numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Calendar month numberName in database: calendar_month_numberOther names:Element type: Data elementDefinition: The number of the month in the calendar year in which this day falls.Context:Relational and representational attributesData type: number Field size: 2 Layout: NNData domain: 1 to 12Guide for use: For example, January is 1.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 25October 2003
  33. 33. GMS Datamart Data Dictionary Global Time tableCalendar quarterAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Calendar quarterName in database: calendar_quarterOther names:Element type: Data elementDefinition: The quarter of the calendar year in which this day falls.Context:Relational and representational attributesData type: varchar Field size: 6 Layout: AAAAAAData domain: first second third fourthGuide for use: For example, January to March is first.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 26October 2003
  34. 34. GMS Datamart Data Dictionary Global Time tableCalendar quarter numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Calendar quarter numberName in database: calendar_quarter_numberOther names:Element type: Data elementDefinition: The number of the quarter of the calendar year in which this day falls.Context:Relational and representational attributesData type: number Field size: 1 Layout: NData domain: 1 to 4Guide for use: For example, January to March is 1.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 27October 2003
  35. 35. GMS Datamart Data Dictionary Global Time tableCalendar yearAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Calendar yearName in database: calendar_yearOther names:Element type: Data elementDefinition: The calendar year in which the date falls.Context:Relational and representational attributesData type: number Field size: 4 Layout: CCYYData domain:Guide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 28October 2003
  36. 36. GMS Datamart Data Dictionary Global Time tableCalendar year and monthAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Calendar year and monthName in database: calendar_year_and_monthOther names:Element type: Data elementDefinition: The calendar year and month in which the date falls.Context:Relational and representational attributesData type: varchar Field size: 6 Layout: CCYYMMData domain:Guide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 29October 2003
  37. 37. GMS Datamart Data Dictionary Global Time tableDay of monthAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Day of monthName in database: day_of_monthOther names:Element type: Data elementDefinition: The day of the month on which this day falls.Context:Relational and representational attributesData type: number Field size: 2 Layout: NNData domain: 1 to 31Guide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 30October 2003
  38. 38. GMS Datamart Data Dictionary Global Time tableDay of weekAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Day of weekName in database: day_of_weekOther names:Element type: Data elementDefinition: The name of the day of the week on which this day falls.Context:Relational and representational attributesData type: varchar Field size: 3 Layout: AAAData domain: Mon to SunGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 31October 2003
  39. 39. GMS Datamart Data Dictionary Global Time tableFinancial month numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Financial month numberName in database: financial_month_numberOther names:Element type: Data elementDefinition: The number of the month in the financial year on which this day falls.Context:Relational and representational attributesData type: number Field size: 2 Layout: NNData domain: 1 to 12Guide for use: For example, July is 1, August is 2, and June is 12.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 32October 2003
  40. 40. GMS Datamart Data Dictionary Global Time tableFinancial quarterAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Financial quarterName in database: financial_quarterOther names:Element type: Data elementDefinition: The quarter of the financial year in which this day falls.Context:Relational and representational attributesData type: varchar Field size: 6 Layout: AAAAAAData domain: first second third fourthGuide for use: For example, July to September is first.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 33October 2003
  41. 41. GMS Datamart Data Dictionary Global Time tableFinancial quarter numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Financial quarter numberName in database: financial_quarter_numberOther names:Element type: Data elementDefinition: The number of the quarter of the financial year in which this day falls.Context:Relational and representational attributesData type: number Field size: 1 Layout: NData domain: 1 to 4Guide for use: For example, July to September is 1.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 34October 2003
  42. 42. GMS Datamart Data Dictionary Global Time tableFinancial yearAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Financial yearName in database: financial_yearOther names:Element type: Data elementDefinition: The financial year in which the day falls, which starts from 1 July and finishes 30 June.Context:Relational and representational attributesData type: varchar Field size: 7 Layout: CCYY/YYData domain:Guide for use: For example, the financial year that begins on 1 July 2000 and ends on 30 June 2001 would be recorded as 2000/01.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 35October 2003
  43. 43. GMS Datamart Data Dictionary Global Time tableMonthAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: MonthName in database: monthOther names:Element type: Data elementDefinition: The short name of the month in which the day falls.Context:Relational and representational attributesData type: varchar Field size: 3 Layout: AAAData domain: Jan to DecGuide for use: The name of the month truncated to three characters, for example Oct.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 36October 2003
  44. 44. GMS Datamart Data Dictionary Global Time tableSQL dateAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: SQL dateName in database: sql_dateOther names:Element type: Data elementDefinition: The date of the day, held as a SQL database date field.Context:Relational and representational attributesData type: datetime Field size: Layout: timestampData domain:Guide for use: The presentation of this field depends on how the viewing software represents dates.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 37October 2003
  45. 45. GMS Datamart Data Dictionary GMS Health Event tableGMS Health Event tableTable name: GMS Health Event tableName in database: fact_gms_healthevent Version: 1.0 Version date: 31-Jul-2003Definition: Contains one record for each accepted claim item (ie, for each visit to a doctor for which a subsidy is claimed).Guide for Use: This is the transaction table for the GMS.Primary Key:Business Key:Relational Rules:Amount claimed (excl GST)Administrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Amount claimed (excl GST)Name in database: amt_claimed_gst_exclOther names:Element type: Data elementDefinition: The amount claimed by the provider for the service, not including GST.Context:Relational and representational attributesData type: number Field size: 11,2 Layout: NNNNNNNNN.NNData domain:Guide for use: HealthPAC provide this value with GST included. The GMS Datamart deducts GST on load.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 38October 2003
  46. 46. GMS Datamart Data Dictionary GMS Health Event tableAmount paid (excl GST)Administrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Amount paid (excl GST)Name in database: amount_paid_gst_exclOther names:Element type: Data elementDefinition: The amount paid to the provider for the service, not including GST.Context:Relational and representational attributesData type: number Field size: 11,2 Layout: NNNNNNNNN.NNData domain:Guide for use: HealthPAC provide this value with GST included. The GMS Datamart deducts GST on load.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 39October 2003
  47. 47. GMS Datamart Data Dictionary GMS Health Event tableInvoice numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Invoice numberName in database: invoice_numberOther names:Element type: Data elementDefinition: The invoice number generated by HealthPAC on behalf of the provider.Context:Relational and representational attributesData type: number Field size: Layout:Data domain:Guide for use: Used to group claims on an invoice.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 40October 2003
  48. 48. GMS Datamart Data Dictionary GMS Health Event tableLocum flagAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Locum flagName in database: locum_flagOther names:Element type: Data elementDefinition: A flag indicating whether the healthcare was provided by a locum.Context:Relational and representational attributesData type: varchar Field size: 1 Layout: AData domain: Y healthcare provided by a locum N healthcare not provided by a locumGuide for use: If Y, then the Provider key refers to the locum.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 41October 2003
  49. 49. GMS Datamart Data Dictionary GMS Health Event tableOriginal item IDAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Original item IDName in database: original_item_idOther names:Element type: Data elementDefinition: Part of the unique key for HealthPAC records.Context:Relational and representational attributesData type: number Field size: Layout:Data domain:Guide for use: Used to identify records for updates. Not unique. This is always 1.Verification rules: The Original message ID, Original transaction ID, and Original item ID form a unique combination.Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 42October 2003
  50. 50. GMS Datamart Data Dictionary GMS Health Event tableOriginal message IDAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Original message IDName in database: original_message_idOther names:Element type: Data elementDefinition: Part of the key for HealthPAC records.Context:Relational and representational attributesData type: char Field size: 12 Layout:Data domain:Guide for use: Used to identify records for update. From the providers point of view, this constitutes a claim.Verification rules: The Original message ID, Original transaction ID, and Original item ID form a unique combination.Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 43October 2003
  51. 51. GMS Datamart Data Dictionary GMS Health Event tableOriginal transaction IDAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Original transaction IDName in database: original_transaction_idOther names:Element type: Data elementDefinition: Part of the unique key for HealthPAC records.Context:Relational and representational attributesData type: number Field size: Layout:Data domain:Guide for use: Used to identify records for updates. Not unique. Starts from 1 for each combination of Original message ID and Original item ID.Verification rules: The Original message ID, Original transaction ID, and Original item ID form a unique combination.Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 44October 2003
  52. 52. GMS Datamart Data Dictionary Healthcare User tableHealthcare User tableTable name: Healthcare User tableName in database: dim_health_care_user Version: 1.0 Version date: 31-Jul-2003Definition: This reference table contains information about all people who have received healthcare directly from healthcare providers.Guide for Use: Contains the encrypted NHI number and demographic details for each healthcare user referenced by the GMS Health Event table. Sourced from the NHI Healthcare User table. Refreshed each month.Primary Key:Business Key:Relational Rules:Date of birthAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Date of birthName in database: date_of_birthOther names: DOB, HCU date of birth, Birth dateElement type: Data elementDefinition: The date on which the person was born.Context: Required to derive age for demographic analyses.Relational and representational attributesData type: datetime Field size: Layout: CCYYMMDDData domain: Valid datesGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 45October 2003
  53. 53. GMS Datamart Data Dictionary Healthcare User tableDate of deathAdministrative statusReference ID: A0026 Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Date of deathName in database: date_of_deathOther names: DOD, Death dateElement type: Data elementDefinition: The date on which the person died.Context:Relational and representational attributesData type: datetime Field size: Layout: CCYYMMDDData domain: Valid datesGuide for use:Verification rules:Collection method: Sourced from the Births, Deaths and Marriages Office.Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 46October 2003
  54. 54. GMS Datamart Data Dictionary Healthcare User tableDeprivation IndexAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Deprivation IndexName in database: deprivation_indexOther names:Element type: Data elementDefinition: A scale of material and social deprivation based on the 1996 census. The Deprivation Index is a combination of nine census variables covering income, transport, living space, owned home, employment, qualifications, support, and communication within a 1996 meshblock.Context:Relational and representational attributesData type: char Field size: 2 Layout: NNData domain: 1 to 10Guide for use: Not usedVerification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 47October 2003
  55. 55. GMS Datamart Data Dictionary Healthcare User tableDHB codeAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB codeName in database: dhb_codeOther names:Element type: Data elementDefinition: District Health Board code as defined by the Senior Advisor, DHB Services, Ministry of Health.Context:Relational and representational attributesData type: varchar Field size: 64 Layout: NNNData domain: 011 Northland 021 Waitemata 022 Auckland 023 Counties Manukau 031 Waikato 042 Lakes 047 Bay of Plenty 051 Tairawhiti 061 Hawkes Bay 071 Taranaki 081 MidCentral 082 Whanganui 091 Capital and Coast 092 Hutt 093 Wairarapa 101 Nelson Marlborough 111 West Coast 121 Canterbury 123 South Canterbury 131 Otago 141 Southland 999 OverseasGuide for use: Derived from NZHIS geocoding of the claimant address. Usually but not always the same as the Funding DHB.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 48October 2003
  56. 56. GMS Datamart Data Dictionary Healthcare User tableDHB nameAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: DHB nameName in database: dhbOther names:Element type: Data elementDefinition: The name of the District Health Board responsible for the domicile.Context:Relational and representational attributesData type: varchar Field size: 64 Layout:Data domain:Guide for use: For completeness, the table includes the Ministry of Health.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 49October 2003
  57. 57. GMS Datamart Data Dictionary Healthcare User tableDomicile codeAdministrative statusReference ID: A0023 Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Domicile codeName in database: domicile_codeOther names:Element type: Data elementDefinition: Statistics NZ Health Domicile Code representing a person’s usual residential address. Also used for facility addresses. Usual residential address is defined as the address at which the person has been, or plans to be, living for 3 months or more. (Statistics NZ definition of ‘usually resident’.) If a person usually lives in a rest home or a hospital, that is considered their usual residential address.Context:Relational and representational attributesData type: char Field size: 4 Layout: XXNNData domain: See the Domicile code table on the NZHIS web site at http://www.nzhis.govt.nz/documentation/codetables.html. For further information or a printed copy of the code table, contact the Publications Officer. Contact details are given at the front of this dictionary.Guide for use: Health Domicile code 2001, which has a one-to-one correspondence to Statistics NZ census area code 2001 but has a maximum of 4 digits instead of 6 digits.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation: Statistics NZVersion: 1.1 NZHIS Page 50October 2003
  58. 58. GMS Datamart Data Dictionary Healthcare User tableDomicile nameAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Domicile nameName in database: domicile_nameOther names:Element type: Data elementDefinition: Health Domicile Name (2001 boundaries).Context:Relational and representational attributesData type: varchar Field size: 64 Layout: Free textData domain:Guide for use: Eg, Akaroa, Pukerua Bay.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 1.1 NZHIS Page 51October 2003
  59. 59. GMS Datamart Data Dictionary Healthcare User tableEncrypted NHI numberAdministrative statusReference ID: Version: 1.0 Version date: 01-Jan-2003Identifying and defining attributesName: Encrypted NHI numberName in database: encrypted_hcu_idOther names: Encrypted HCU identifier, Encrypted NHI, etc. See other names for the NHI number under Guide for use.Element type: Data elementDefinition: The NHI number in encrypted form.Context: The NHI number is the cornerstone of NZHIS’s data collections. It is a unique 7-character identification number assigned to a healthcare user by the National Health Index (NHI) database. The NHI number uniquely identifies healthcare users, and allows linking between different data collections. It is encrypted in Labs to ensure privacy of individual records.Relational and representational attributesData type: varchar Field size: 11 Layout:Data domain: System-generatedGuide for use: THE NHI NUMBER The NHI number is also known as National Health Index, HCU identifier, NHI, HCU, HCU Number, Healthcare User identifier, HCU identification number, NMPI number, Hospital Number, Patient Number. When duplicate records for a healthcare user are merged, one of their NHI numbers will be deemed to be the master (or primary), and the others become event (or secondary) NHI numbers. This does not affect which NHI numbers are used in local systems. The NHI number that is sent in by the data provider is encrypted during the loading process. Only this encrypted NHI number is stored. For the analysis of healthcare information relating to a unique individual, the master NHI number should be used. Please contact inquiries@nzhis.co.nz for further information on how to obtain the master encrypted NHI number if you are performing your own data extraction. The Privacy Commissioner considers the NHI number to be personally identifying information (like name and address) so, if it is linked to clinical information, it must be held securely and the healthcare user’s privacy protected. The Encrypted NHI number is not considered personally identifying. NZHIS will return data containing unencrypted NHI numbers to providers who have sent it in. Information available to the general public is of a statistical and non-identifiable nature. Researchers requiring identifiable data will usually need approval from an Ethics Committee. VALIDATION The first three characters of an NHI number must be alpha (but not I or O). The 4th to 6th characters must be numeric. The 7th character is a check digit modulus 11. ENCRYPTION The NHI number is encrypted using a one-way encryption algorithm. The aim is to provide an encrypted number that can be sent across public (unsecured) networks.Verification rules: Must be registered on the NHI before use. There is a verification algorithm which ensures that the NHI number is in the correct format and is valid.Collection method: NHI numbers are often included on patient notes and other patient documentation. New numbers can be allocated by health providers who have direct access to the NHI Register.Version: 1.1 NZHIS Page 52October 2003
  60. 60. GMS Datamart Data Dictionary Healthcare User tableRelated data:Administrative attributesSource document: http://www.nzhis.govt.nz/nhi/ for more information on the NHI numberSource organisation: NZHISVersion: 1.1 NZHIS Page 53October 2003

×