This document provides an introduction and overview of the Ministry of Health's Shared Dimensions Data Dictionary. The dictionary contains definitions for data elements collected across multiple health datasets in New Zealand. It aims to promote consistency, standard definitions, and support use of nationally agreed protocols. The dictionary follows a standardized format and includes details like historical information, related data, and code tables for each data element defined.
This document provides a data dictionary for the General Medical Subsidy Datamart (GMS) which contains information on medical claims and contracts in New Zealand. It describes the tables and data elements in the GMS, including definitions of coding systems, relationships between data, and background information on data collection. Guidelines are provided for using the data, noting that not all described elements may be present in all reporting outputs. Contact information is included for queries about the data dictionary.
sumandro_anatomy_of_nsso_data_opendatacamp_20120324Sumandro C
Presentation made at OpenDataCamp in Bangalore (24th March 2012) on the organisation of unit-level data published by National Sample Survey Organisation, Govt. of India.
sumandro_the_art_of_nsso_data_5thelephant_20120728Sumandro C
Presentation made at The Fifth Elephant conference organised by HasGeek in July 2012, on structure of data published by the National Sample Survey Office, Govt of India, and its extraction using R.
The New Zealand Cancer Registry (NZCR) contains information on cancers diagnosed in New Zealand. This includes demographic data, details on cancer diagnosis and treatment, and follow-up information. The NZCR aims to monitor cancer trends and support research. Data is collected from pathology laboratories, hospitals, and mortality records. Strict privacy protocols are followed to protect individuals' health information.
Urm concept for sharing information inside of communitiesKarel Charvat
The document describes the Uniform Resource Management (URM) concept for sharing information within communities. URM provides a framework for standardized description of information using metadata schemes and controlled vocabularies to improve discovery. It is implemented through various portals and tools that allow users to manage and discover knowledge according to context. Initial implementations included portals for nature, sustainability and rural information in the Czech Republic and Latvia. URM supports collaborative knowledge sharing through interoperable systems based on open standards.
Presentation at NeHC: Overview of ONC's health information exchange standards-selection activities. Focuses on HITSC, the S&I Framework, and the S&I Query Health Initiative.
NIH iDASH meeting on data sharing - BioSharing, ISA and Scientific DataSusanna-Assunta Sansone
1) The document discusses Susanna-Assunta Sansone's roles and work related to promoting FAIR data standards and practices.
2) It highlights some of her leadership positions with organizations like BioSharing that work to map and promote standards.
3) The document also discusses Scientific Data, a peer-reviewed journal launched by Nature Publishing Group to publish detailed descriptions of scientifically valuable datasets to facilitate reuse.
This document provides a data dictionary for the General Medical Subsidy Datamart (GMS) which contains information on medical claims and contracts in New Zealand. It describes the tables and data elements in the GMS, including definitions of coding systems, relationships between data, and background information on data collection. Guidelines are provided for using the data, noting that not all described elements may be present in all reporting outputs. Contact information is included for queries about the data dictionary.
sumandro_anatomy_of_nsso_data_opendatacamp_20120324Sumandro C
Presentation made at OpenDataCamp in Bangalore (24th March 2012) on the organisation of unit-level data published by National Sample Survey Organisation, Govt. of India.
sumandro_the_art_of_nsso_data_5thelephant_20120728Sumandro C
Presentation made at The Fifth Elephant conference organised by HasGeek in July 2012, on structure of data published by the National Sample Survey Office, Govt of India, and its extraction using R.
The New Zealand Cancer Registry (NZCR) contains information on cancers diagnosed in New Zealand. This includes demographic data, details on cancer diagnosis and treatment, and follow-up information. The NZCR aims to monitor cancer trends and support research. Data is collected from pathology laboratories, hospitals, and mortality records. Strict privacy protocols are followed to protect individuals' health information.
Urm concept for sharing information inside of communitiesKarel Charvat
The document describes the Uniform Resource Management (URM) concept for sharing information within communities. URM provides a framework for standardized description of information using metadata schemes and controlled vocabularies to improve discovery. It is implemented through various portals and tools that allow users to manage and discover knowledge according to context. Initial implementations included portals for nature, sustainability and rural information in the Czech Republic and Latvia. URM supports collaborative knowledge sharing through interoperable systems based on open standards.
Presentation at NeHC: Overview of ONC's health information exchange standards-selection activities. Focuses on HITSC, the S&I Framework, and the S&I Query Health Initiative.
NIH iDASH meeting on data sharing - BioSharing, ISA and Scientific DataSusanna-Assunta Sansone
1) The document discusses Susanna-Assunta Sansone's roles and work related to promoting FAIR data standards and practices.
2) It highlights some of her leadership positions with organizations like BioSharing that work to map and promote standards.
3) The document also discusses Scientific Data, a peer-reviewed journal launched by Nature Publishing Group to publish detailed descriptions of scientifically valuable datasets to facilitate reuse.
Designing and launching the Clinical Reference LibraryKerstin Forsberg
Presentation for the European Clinical Data Forum conference, 24 May, 2011. Describing the business problems and drivers behind the design of a ISO11179 based metadata registry for clinical data. And also introducing the features of the CRL application.
Semantic interoperability courses training module 3 - reference data v0.10Semic.eu
By the end of this training you should have an understanding of:
What reference data is, its context and purpose and how it creates value for organisations.
Why it is important to manage and govern the reference data lifecycle.
How to work with reference data using open-source tools.
Alain Frey Research Data for universities and information producersIncisive_Events
Research data is growing exponentially but is disparate and challenging to understand fully. Universities face challenges in managing research data to meet funding and standards requirements. Thomson Reuters launched the Data Citation Index to make research data discoverable, accessible, and citable by bringing important data from diverse repositories into one searchable index. This addresses the need for a single access point for quality research data across disciplines and locations.
The Diversity of Biomedical Data, Databases and Standards (Research Data Alli...Peter McQuilton
A 10 minute presentation given in Denver (CO) on the 15th September as part of the IG Elixir Bridging Force, WG Biosharing Registry,WG Data Type Registries,WG Metadata Standards Catalog joint session of the Research Data Alliance 8th Plenary (part of International Data Week).
This presentation covers the proliferation of data, databases, and data standards in biomedicine, and how BioSharing can help inform and educate users on this landscape and relationships between data, databases and data standards.
WHAT ARE METADATA STANDARDS? EXPLAIN DUBLIN CORE IN DETAIL.`Shweta Bhavsar
This document discusses metadata standards and provides details on Dublin Core. It defines metadata as "structured data about data" and explains its role in digital resource management. It outlines different types of metadata standards including descriptive, structural, and administrative. Dublin Core is introduced as a general metadata standard consisting of 15 elements used to describe resources. It was developed in 1995 to make it easy to discover web resources by providing a simple yet flexible set of elements for description. The document provides details on the development and governance of Dublin Core as well as its two forms: simple Dublin Core with 15 elements, and qualified Dublin Core which includes additional elements and properties.
Scientific Data overview of Data Descriptors - WT Data-Literature integration...Susanna-Assunta Sansone
This document introduces Scientific Data, a new peer-reviewed journal for publishing data descriptors from Nature Publishing Group. It will provide structured metadata and narrative articles to describe datasets for reuse. The journal is now open for submissions and will launch in May 2014, featuring an advisory panel and sections for standardized data descriptor articles and experimental metadata. It aims to give proper credit for data sharing and promote open access, reuse and peer review of curated scientific datasets.
Presentation to the EC Workshop on Maximizing investments in health research: FAIR data for a coordinate COVID-19 response. Workshop I, October 11, 2021.
An update on the latest BioSharing work; including work with ELIXIR and NIH BD2K, also our survey to assess user needs (530 replies) and the work on the recommender tool
Neuroinformatics_Databses_Ontologies_Federated Database.pptxJagannath University
This will introduce and describe NIF(Neuroscience information framework), Federated databases, data federation vs data warehouse, ontology, ontology vs database, steps in creating ontology.
Neuroinformatics Databases Ontologies Federated Database.pptxJagannath University
Neuroscience Information Framework(NIF), Federated Database, Data Federation vs Data warehouse, ontology, steps in creating ontology, ontology vs database
This document provides guidance on creating a Data Management Plan (DMP). It discusses the key elements that should be included in a DMP, such as the types of data that will be collected, metadata standards, data sharing and access policies, plans for reusing and redistributing data, and archiving data for long-term preservation. It also notes that costs for implementing the DMP may be included in the proposal budget and that the DMP will be reviewed as part of the NSF proposal process. Template codes for elements like variable names and labels that could be included in a DMP are also provided.
The document provides an overview of the Integrating the Healthcare Enterprise (IHE) Integration Profile called Cross-Enterprise Document Sharing (XDS). XDS allows for the registration, distribution and access of patient electronic health records across different healthcare organizations. It defines standards for managing the sharing of clinical documents between any healthcare enterprise, regardless of where the documents or systems reside. The document describes the main XDS actors, transactions, use cases and technical standards involved in cross-enterprise clinical document sharing using XDS.
Dr. Tito Castillo discusses challenges with data discovery and sharing at University College London Hospitals (UCLH) due to their multiple proprietary clinical systems with undocumented data and data warehouses. To address this, UCLH is taking a standards-based approach using models like DDI and SDMX to document metadata and map their processes. The goal is to enable better data access, sharing, and reuse to support research programmes and new models of care while respecting governance and privacy.
This document summarizes a presentation by Timothy Hoctor, VP of Professional Services at Elsevier, about Elsevier's strategic vision and professional services. The key points are:
1) Elsevier aims to increase R&D productivity by linking data across the development spectrum and increase return on information through enhanced search and visualization tools.
2) Elsevier's Professional Services team leverages Elsevier's capabilities to provide customized data management and analysis solutions.
3) Elsevier's strategic objective is to become a leading collaborator in R&D data management through services like data mapping, gap analysis, data governance, and integrated data management.
Chapter 12 Page 209Discussion Questions 2. How does a d.docxcravennichole326
Chapter 12 Page 209
Discussion Questions
2. How does a data dictionary influence the design and implementation of an EHR? How does the data dictionary enhance and restrict the EHR?
3. In what circumstances might a clinical infrastructure based on either third-party service providers or mobile applications be desirable? What cautions would we place on these technologies in the same circumstances?
Chapter 12 Page 209
Discussion Questions
2. How does a data dictio
nary influence the design and implementation of an EHR? How does the data
dictionary enhance and restrict the EHR?
3. In what circumstances might a clinical infrastructure based on either third
-
party service providers
or mobile applications be desirabl
e? What cautions would we place on these technologies in the same
circumstances?
Chapter 12 Page 209
Discussion Questions
2. How does a data dictionary influence the design and implementation of an EHR? How does the data
dictionary enhance and restrict the EHR?
3. In what circumstances might a clinical infrastructure based on either third-party service providers
or mobile applications be desirable? What cautions would we place on these technologies in the same
circumstances?
Chapter 12 Technical Infrastructure to Support Healthcare
Scott P. Narus
No single off-the-shelf system today can support all needs of the healthcare environment. Therefore it is critical that the technical architecture be capable of supporting multiple system connections and data interoperability.
Objectives
At the completion of this chapter the reader will be prepared to:
1.Describe the key technical components of electronic health records and their interrelationships
2.Define interoperability and its major elements
3.Contrast networking arrangements such as regional health information organizations (RHIOs), health information exchanges (HIEs), and health information organizations (HIOs)
4.Provide information about newer technical models such as cloud computing and application service providers (ASPs)
5.Synthesize current challenges for informatics infrastructure
Key Terms
Application service provider (ASP), 205
Architecture, 197
Clinical data repository (CDR), 198
Cloud computing, 205
Data dictionary, 201
Health information organization (HIO), 204
Infrastructure, 197
Interface engine (IE), 203
Knowledge base, 202
Master person index (MPI), 199
Regional Health Information Organization (RHIO), 204
Service-oriented architecture (SOA), 207
Abstract
This chapter introduces the technical aspects of electronic health records (EHRs) and the current infrastructure components. Complementing the functional components discussed elsewhere, this chapter introduces terms such as clinical data repository, master person index, interface engine, and data dictionary and other technical components necessary for EHRs to function. Recent material about national efforts related to the infrastructure and electroni ...
The students conducted a survey to develop a blood bank management software system. They visited a local blood bank to collect information and referred to international standards. They gathered forms, testing procedures, and module requirements. An entity relationship diagram was created linking donor, patient, and blood bank data. A data flow diagram was also prepared showing the flow of information between the blood bank and hospitals. The survey findings helped inform the design and implementation of the blood bank management software project.
This document provides an overview of metadata and data standards developed for the health domain in India. It describes the need for common data standards to promote interoperability across health IT applications. The standards are organized into four parts, with Part I being an overview. The standards were developed following international guidelines and include around 1000 common data elements grouped under 39 entities. Code directories with standardized codes are also included to enforce data standards. The implementation of the standards requires an institutional framework including a national health authority.
Access the webinar: http://goo.gl/p08pTz
These slides were presented in a webinar by Denodo in collaboration with BioStorage Technologies and Indiana Clinical and Translational Sciences Institute and Regenstrief Institute.
BioStorage Technologies, Inc., Indiana Clinical and Translational Sciences Institute, and Regenstrief Institute (CTSI) have joined Denodo to talk about the important role of technological advancements, such as data virtualization, in advancing biospecimen research.
By watching this webinar, you can gain insight into best practices around the integration of biospecimen and research data as well as technology solutions that provide consolidated views and rapid conversions of this data into valuable business insights. You will also learn how data virtualization can assist with the integration of data residing in heterogeneous repositories and can securely deliver aggregated data in real-time.
Designing and launching the Clinical Reference LibraryKerstin Forsberg
Presentation for the European Clinical Data Forum conference, 24 May, 2011. Describing the business problems and drivers behind the design of a ISO11179 based metadata registry for clinical data. And also introducing the features of the CRL application.
Semantic interoperability courses training module 3 - reference data v0.10Semic.eu
By the end of this training you should have an understanding of:
What reference data is, its context and purpose and how it creates value for organisations.
Why it is important to manage and govern the reference data lifecycle.
How to work with reference data using open-source tools.
Alain Frey Research Data for universities and information producersIncisive_Events
Research data is growing exponentially but is disparate and challenging to understand fully. Universities face challenges in managing research data to meet funding and standards requirements. Thomson Reuters launched the Data Citation Index to make research data discoverable, accessible, and citable by bringing important data from diverse repositories into one searchable index. This addresses the need for a single access point for quality research data across disciplines and locations.
The Diversity of Biomedical Data, Databases and Standards (Research Data Alli...Peter McQuilton
A 10 minute presentation given in Denver (CO) on the 15th September as part of the IG Elixir Bridging Force, WG Biosharing Registry,WG Data Type Registries,WG Metadata Standards Catalog joint session of the Research Data Alliance 8th Plenary (part of International Data Week).
This presentation covers the proliferation of data, databases, and data standards in biomedicine, and how BioSharing can help inform and educate users on this landscape and relationships between data, databases and data standards.
WHAT ARE METADATA STANDARDS? EXPLAIN DUBLIN CORE IN DETAIL.`Shweta Bhavsar
This document discusses metadata standards and provides details on Dublin Core. It defines metadata as "structured data about data" and explains its role in digital resource management. It outlines different types of metadata standards including descriptive, structural, and administrative. Dublin Core is introduced as a general metadata standard consisting of 15 elements used to describe resources. It was developed in 1995 to make it easy to discover web resources by providing a simple yet flexible set of elements for description. The document provides details on the development and governance of Dublin Core as well as its two forms: simple Dublin Core with 15 elements, and qualified Dublin Core which includes additional elements and properties.
Scientific Data overview of Data Descriptors - WT Data-Literature integration...Susanna-Assunta Sansone
This document introduces Scientific Data, a new peer-reviewed journal for publishing data descriptors from Nature Publishing Group. It will provide structured metadata and narrative articles to describe datasets for reuse. The journal is now open for submissions and will launch in May 2014, featuring an advisory panel and sections for standardized data descriptor articles and experimental metadata. It aims to give proper credit for data sharing and promote open access, reuse and peer review of curated scientific datasets.
Presentation to the EC Workshop on Maximizing investments in health research: FAIR data for a coordinate COVID-19 response. Workshop I, October 11, 2021.
An update on the latest BioSharing work; including work with ELIXIR and NIH BD2K, also our survey to assess user needs (530 replies) and the work on the recommender tool
Neuroinformatics_Databses_Ontologies_Federated Database.pptxJagannath University
This will introduce and describe NIF(Neuroscience information framework), Federated databases, data federation vs data warehouse, ontology, ontology vs database, steps in creating ontology.
Neuroinformatics Databases Ontologies Federated Database.pptxJagannath University
Neuroscience Information Framework(NIF), Federated Database, Data Federation vs Data warehouse, ontology, steps in creating ontology, ontology vs database
This document provides guidance on creating a Data Management Plan (DMP). It discusses the key elements that should be included in a DMP, such as the types of data that will be collected, metadata standards, data sharing and access policies, plans for reusing and redistributing data, and archiving data for long-term preservation. It also notes that costs for implementing the DMP may be included in the proposal budget and that the DMP will be reviewed as part of the NSF proposal process. Template codes for elements like variable names and labels that could be included in a DMP are also provided.
The document provides an overview of the Integrating the Healthcare Enterprise (IHE) Integration Profile called Cross-Enterprise Document Sharing (XDS). XDS allows for the registration, distribution and access of patient electronic health records across different healthcare organizations. It defines standards for managing the sharing of clinical documents between any healthcare enterprise, regardless of where the documents or systems reside. The document describes the main XDS actors, transactions, use cases and technical standards involved in cross-enterprise clinical document sharing using XDS.
Dr. Tito Castillo discusses challenges with data discovery and sharing at University College London Hospitals (UCLH) due to their multiple proprietary clinical systems with undocumented data and data warehouses. To address this, UCLH is taking a standards-based approach using models like DDI and SDMX to document metadata and map their processes. The goal is to enable better data access, sharing, and reuse to support research programmes and new models of care while respecting governance and privacy.
This document summarizes a presentation by Timothy Hoctor, VP of Professional Services at Elsevier, about Elsevier's strategic vision and professional services. The key points are:
1) Elsevier aims to increase R&D productivity by linking data across the development spectrum and increase return on information through enhanced search and visualization tools.
2) Elsevier's Professional Services team leverages Elsevier's capabilities to provide customized data management and analysis solutions.
3) Elsevier's strategic objective is to become a leading collaborator in R&D data management through services like data mapping, gap analysis, data governance, and integrated data management.
Chapter 12 Page 209Discussion Questions 2. How does a d.docxcravennichole326
Chapter 12 Page 209
Discussion Questions
2. How does a data dictionary influence the design and implementation of an EHR? How does the data dictionary enhance and restrict the EHR?
3. In what circumstances might a clinical infrastructure based on either third-party service providers or mobile applications be desirable? What cautions would we place on these technologies in the same circumstances?
Chapter 12 Page 209
Discussion Questions
2. How does a data dictio
nary influence the design and implementation of an EHR? How does the data
dictionary enhance and restrict the EHR?
3. In what circumstances might a clinical infrastructure based on either third
-
party service providers
or mobile applications be desirabl
e? What cautions would we place on these technologies in the same
circumstances?
Chapter 12 Page 209
Discussion Questions
2. How does a data dictionary influence the design and implementation of an EHR? How does the data
dictionary enhance and restrict the EHR?
3. In what circumstances might a clinical infrastructure based on either third-party service providers
or mobile applications be desirable? What cautions would we place on these technologies in the same
circumstances?
Chapter 12 Technical Infrastructure to Support Healthcare
Scott P. Narus
No single off-the-shelf system today can support all needs of the healthcare environment. Therefore it is critical that the technical architecture be capable of supporting multiple system connections and data interoperability.
Objectives
At the completion of this chapter the reader will be prepared to:
1.Describe the key technical components of electronic health records and their interrelationships
2.Define interoperability and its major elements
3.Contrast networking arrangements such as regional health information organizations (RHIOs), health information exchanges (HIEs), and health information organizations (HIOs)
4.Provide information about newer technical models such as cloud computing and application service providers (ASPs)
5.Synthesize current challenges for informatics infrastructure
Key Terms
Application service provider (ASP), 205
Architecture, 197
Clinical data repository (CDR), 198
Cloud computing, 205
Data dictionary, 201
Health information organization (HIO), 204
Infrastructure, 197
Interface engine (IE), 203
Knowledge base, 202
Master person index (MPI), 199
Regional Health Information Organization (RHIO), 204
Service-oriented architecture (SOA), 207
Abstract
This chapter introduces the technical aspects of electronic health records (EHRs) and the current infrastructure components. Complementing the functional components discussed elsewhere, this chapter introduces terms such as clinical data repository, master person index, interface engine, and data dictionary and other technical components necessary for EHRs to function. Recent material about national efforts related to the infrastructure and electroni ...
The students conducted a survey to develop a blood bank management software system. They visited a local blood bank to collect information and referred to international standards. They gathered forms, testing procedures, and module requirements. An entity relationship diagram was created linking donor, patient, and blood bank data. A data flow diagram was also prepared showing the flow of information between the blood bank and hospitals. The survey findings helped inform the design and implementation of the blood bank management software project.
This document provides an overview of metadata and data standards developed for the health domain in India. It describes the need for common data standards to promote interoperability across health IT applications. The standards are organized into four parts, with Part I being an overview. The standards were developed following international guidelines and include around 1000 common data elements grouped under 39 entities. Code directories with standardized codes are also included to enforce data standards. The implementation of the standards requires an institutional framework including a national health authority.
Access the webinar: http://goo.gl/p08pTz
These slides were presented in a webinar by Denodo in collaboration with BioStorage Technologies and Indiana Clinical and Translational Sciences Institute and Regenstrief Institute.
BioStorage Technologies, Inc., Indiana Clinical and Translational Sciences Institute, and Regenstrief Institute (CTSI) have joined Denodo to talk about the important role of technological advancements, such as data virtualization, in advancing biospecimen research.
By watching this webinar, you can gain insight into best practices around the integration of biospecimen and research data as well as technology solutions that provide consolidated views and rapid conversions of this data into valuable business insights. You will also learn how data virtualization can assist with the integration of data residing in heterogeneous repositories and can securely deliver aggregated data in real-time.
3. Shared Dimensions Data Dictionary Shared Dimensions
Introduction
Objectives The objectives of the Ministry of Health (‘the Ministry’) 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 Data Dictionaries are data providers,
software developers, and data users.
Format
All data element definitions in the 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 the appendices 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 Ministry’s web site (for large or dynamic code
tables).
Version 2.3 MoH 2
January 2010
4. Shared Dimensions Data Dictionary Shared Dimensions
Table of Contents
Shared Dimensions...................................................................................................................................9
Affiliation table.........................................................................................................................................10
Ethnic code 1 .....................................................................................................................................11
Ethnic code 2 .....................................................................................................................................13
Ethnic code 3 .....................................................................................................................................14
Ethnicity 1...........................................................................................................................................15
Ethnicity 2...........................................................................................................................................16
Ethnicity 3...........................................................................................................................................17
Gender ...............................................................................................................................................18
Gender Code......................................................................................................................................19
Level 0 ethnic code 1 .........................................................................................................................20
Level 0 ethnic code 2 .........................................................................................................................21
Level 0 ethnic code 3 .........................................................................................................................22
Level 0 ethnicity 1 ..............................................................................................................................23
Level 0 ethnicity 2 ..............................................................................................................................24
Level 0 ethnicity 3 ..............................................................................................................................25
Level 1 ethnic code 1 .........................................................................................................................26
Level 1 ethnic code 2 .........................................................................................................................27
Level 1 ethnic code 3 .........................................................................................................................28
Level 1 ethnicity 1 ..............................................................................................................................29
Level 1 ethnicity 2 ..............................................................................................................................30
Level 1 ethnicity 3 ..............................................................................................................................31
Priority ethnicity..................................................................................................................................32
Priority ethnicity code .........................................................................................................................33
level 0 priority ethnic code..................................................................................................................34
level 0 priority ethnicity .......................................................................................................................35
level 1 priority ethnic code..................................................................................................................36
level 1 priority ethnicity .......................................................................................................................37
Age Band table .......................................................................................................................................38
(Capitated) Funding Band ..................................................................................................................39
Age in years .......................................................................................................................................40
Five year band ...................................................................................................................................41
General Medical Subsidy Age Band...................................................................................................42
Life Stage band ..................................................................................................................................43
Maternity band ...................................................................................................................................44
Ten year band ....................................................................................................................................45
Agency Facility table ...............................................................................................................................46
Agency Facility BK .............................................................................................................................47
Agency address .................................................................................................................................48
Agency closing date ...........................................................................................................................49
Agency code ......................................................................................................................................50
Agency name .....................................................................................................................................51
Agency open date ..............................................................................................................................52
Agency type code...............................................................................................................................53
Agency type description .....................................................................................................................54
DHB code...........................................................................................................................................55
DHB name..........................................................................................................................................56
Domicile code.....................................................................................................................................57
Facility Address..................................................................................................................................58
Facility Code ......................................................................................................................................59
Facility close date...............................................................................................................................60
Facility name ......................................................................................................................................61
Facility open date ...............................................................................................................................62
Facility type ........................................................................................................................................63
Facility type description......................................................................................................................64
Region................................................................................................................................................65
ANZSCO dimension table.......................................................................................................................66
ANZSCO code ...................................................................................................................................67
ANZSCO description..........................................................................................................................68
Category 1..........................................................................................................................................69
Category 2..........................................................................................................................................70
Category 3..........................................................................................................................................71
Version 2.3 MoH 3
January 2010
5. Shared Dimensions Data Dictionary Shared Dimensions
Category 4..........................................................................................................................................72
Category 5..........................................................................................................................................73
Census Affiliation table ...........................................................................................................................74
Gender ...............................................................................................................................................75
Gender code ......................................................................................................................................76
Level 0 priority ethnic code.................................................................................................................77
Level 0 priority ethnicity......................................................................................................................78
Level 1 priority ethnic code.................................................................................................................79
Level 1 priority ethnicity......................................................................................................................80
Census Geofile table...............................................................................................................................81
DHB code...........................................................................................................................................82
DHB name..........................................................................................................................................83
Domicile code 2001............................................................................................................................84
Domicile name ...................................................................................................................................85
Health district name ...........................................................................................................................86
Nzdep 01............................................................................................................................................87
Public health provider name...............................................................................................................88
TLA name...........................................................................................................................................89
Claim Code table ....................................................................................................................................90
CSC Flag............................................................................................................................................91
Claim code .........................................................................................................................................92
Description .........................................................................................................................................93
HUHC Flag.........................................................................................................................................94
Patient category .................................................................................................................................95
Clinical Code table ..................................................................................................................................96
Block ..................................................................................................................................................97
Block Long Description.......................................................................................................................98
Block publication description ..............................................................................................................99
Block short description .....................................................................................................................100
Category...........................................................................................................................................101
Category long description.................................................................................................................102
Category publication ........................................................................................................................103
Category short description ...............................................................................................................104
Chapter ............................................................................................................................................105
Chapter description ..........................................................................................................................106
Clinical code.....................................................................................................................................108
Clinical code description...................................................................................................................111
Clinical code type .............................................................................................................................112
Clinical code type description...........................................................................................................113
Clinical coding system ID .................................................................................................................114
Clinical system description ...............................................................................................................116
Code end date..................................................................................................................................117
Code start date.................................................................................................................................118
Collection type..................................................................................................................................119
Dagger asterisk ................................................................................................................................120
Death flag.........................................................................................................................................121
Eligible cancer status .......................................................................................................................122
External cause flag...........................................................................................................................123
High age...........................................................................................................................................124
Low age............................................................................................................................................125
Non-specific diagnosis flag...............................................................................................................126
Normal NZ flag .................................................................................................................................127
Operation flag...................................................................................................................................128
Sex flag ............................................................................................................................................129
Sub chapter description....................................................................................................................130
Sub-category....................................................................................................................................131
Sub-chapter......................................................................................................................................132
Unacceptable diagnosis flag ............................................................................................................133
Contract Details table............................................................................................................................134
Allow payment..................................................................................................................................135
Change flag......................................................................................................................................136
Contract description .........................................................................................................................137
Contract expiry date .........................................................................................................................138
Contract number ..............................................................................................................................139
Version 2.3 MoH 4
January 2010
6. Shared Dimensions Data Dictionary Shared Dimensions
Contract type....................................................................................................................................140
Current version.................................................................................................................................141
DHB code.........................................................................................................................................142
Payment days ..................................................................................................................................143
Payment term code ..........................................................................................................................144
Perorg ID..........................................................................................................................................145
Country table.........................................................................................................................................146
Country code description..................................................................................................................147
Country of Birth ................................................................................................................................148
DHB Reference table ............................................................................................................................149
DHB ID .............................................................................................................................................150
DHB code.........................................................................................................................................151
DHB name........................................................................................................................................152
dhb ssg.............................................................................................................................................153
Diagnosis Type table ............................................................................................................................154
Diagnosis type..................................................................................................................................155
Diagnosis type description ...............................................................................................................157
DRG table .............................................................................................................................................158
DRG code ........................................................................................................................................159
DRG code description ......................................................................................................................160
DRG grouper type code ...................................................................................................................161
DRG grouper type description..........................................................................................................162
MDC code ........................................................................................................................................163
MDC description...............................................................................................................................164
drg category code ............................................................................................................................165
Ethnicity table........................................................................................................................................166
Ethnic Code......................................................................................................................................167
Ethnicity............................................................................................................................................168
Level 0 ethnic code ..........................................................................................................................169
Level 0 ethnicity ...............................................................................................................................170
Level 1 ethnic code ..........................................................................................................................171
Level 1 ethnicity ...............................................................................................................................172
Event End Type table............................................................................................................................173
Event end description.......................................................................................................................174
Event end type code ........................................................................................................................175
Separation mode..............................................................................................................................178
Event Type table ...................................................................................................................................179
Event type code ...............................................................................................................................180
Event type description......................................................................................................................181
Facility Type table .................................................................................................................................182
Facility Type description...................................................................................................................183
Facility type ......................................................................................................................................184
Geo table ..............................................................................................................................................185
Area unit...........................................................................................................................................186
Area unit code ..................................................................................................................................187
Census year .....................................................................................................................................188
DHB code.........................................................................................................................................189
DHB name........................................................................................................................................190
Domicile code...................................................................................................................................191
Domicile name .................................................................................................................................192
HHS..................................................................................................................................................193
HHS code.........................................................................................................................................194
Locality .............................................................................................................................................195
Locality code ....................................................................................................................................196
Nzdep 2001......................................................................................................................................197
RHA code.........................................................................................................................................198
Region..............................................................................................................................................199
Rural status code .............................................................................................................................200
Sub-locality.......................................................................................................................................201
Sub-locality code..............................................................................................................................202
Territorial Authority...........................................................................................................................203
Territorial Authority code ..................................................................................................................204
Version 2.3 MoH 5
January 2010
7. Shared Dimensions Data Dictionary Shared Dimensions
Year retired ......................................................................................................................................205
Geofile table..........................................................................................................................................206
Area Unit 1991 .................................................................................................................................207
Area Unit 1996 .................................................................................................................................208
Area Unit 2001 NZDEP ....................................................................................................................209
Area Unit 2006 .................................................................................................................................210
Area unit name.................................................................................................................................211
DHB code.........................................................................................................................................212
DHB name........................................................................................................................................213
Domicile code 1991..........................................................................................................................214
Domicile code 1996..........................................................................................................................215
Domicile code 2001..........................................................................................................................216
Domicile code 2006..........................................................................................................................217
Domicile name .................................................................................................................................218
Health district ...................................................................................................................................219
Mesh Block 1991..............................................................................................................................220
Mesh Block 1996..............................................................................................................................221
Mesh block 2001 ..............................................................................................................................222
Mesh block 2006 ..............................................................................................................................223
Nzdep 01..........................................................................................................................................224
Nzdep 96..........................................................................................................................................225
Post code .........................................................................................................................................226
Public health provider.......................................................................................................................227
RHA..................................................................................................................................................228
TLA Code 1995 ................................................................................................................................229
TLA name.........................................................................................................................................230
Ward 1995........................................................................................................................................231
Ward Name ......................................................................................................................................232
area unit 2001 ..................................................................................................................................233
Global Time table..................................................................................................................................234
Calendar month key .........................................................................................................................235
Calendar month number...................................................................................................................236
Calendar quarter ..............................................................................................................................237
Calendar quarter number .................................................................................................................238
Calendar year...................................................................................................................................239
Calendar year and month.................................................................................................................240
Calendar year and quarter ...............................................................................................................241
Day of month....................................................................................................................................242
Day of week .....................................................................................................................................243
Financial month number...................................................................................................................244
Financial quarter ..............................................................................................................................245
Financial quarter number .................................................................................................................246
Financial year...................................................................................................................................247
Financial year and quarter................................................................................................................248
First day of month ............................................................................................................................249
Global time dim key..........................................................................................................................250
Last day of month.............................................................................................................................251
Month ...............................................................................................................................................252
SQL date ..........................................................................................................................................253
Time key...........................................................................................................................................254
HCU Identifiable table ...........................................................................................................................255
Address Line 1 .................................................................................................................................256
Address Line 2 .................................................................................................................................257
Address Line 3 .................................................................................................................................258
Address Line 4 .................................................................................................................................259
Address Line 5 .................................................................................................................................260
Date of birth......................................................................................................................................261
Date of death....................................................................................................................................262
Dim HCU Identifiable key .................................................................................................................263
Dim affiliation key .............................................................................................................................264
Ethnic code 1 ...................................................................................................................................265
Ethnic code 2 ...................................................................................................................................266
Ethnic code 3 ...................................................................................................................................267
Family Name ....................................................................................................................................268
First name ........................................................................................................................................269
Version 2.3 MoH 6
January 2010
8. Shared Dimensions Data Dictionary Shared Dimensions
Gender Code....................................................................................................................................270
HCU id..............................................................................................................................................271
Priority ethnic code...........................................................................................................................272
Second Name ..................................................................................................................................273
Third Name ......................................................................................................................................274
master hcu id....................................................................................................................................275
Health Care User table .........................................................................................................................276
Date of birth......................................................................................................................................277
Date of death....................................................................................................................................278
Dim affiliation key .............................................................................................................................279
Encrypted hcu id ..............................................................................................................................280
Ethnic code 1 ...................................................................................................................................282
Ethnic code 2 ...................................................................................................................................284
Ethnic code 3 ...................................................................................................................................285
Gender code ....................................................................................................................................286
Master encrypted hcu id ...................................................................................................................287
Priority ethnic code...........................................................................................................................289
dim hcu key ......................................................................................................................................290
dss_count_distinct............................................................................................................................291
Health Specialty table ...........................................................................................................................292
Health specialty code .......................................................................................................................293
Health specialty description..............................................................................................................294
Health specialty end date .................................................................................................................295
Health specialty start date ................................................................................................................296
Mental health inpatient flag ..............................................................................................................297
Specialty full description...................................................................................................................298
Legal Status table .................................................................................................................................299
Legal status act code .......................................................................................................................300
Legal status act description..............................................................................................................301
Legal status code .............................................................................................................................302
Legal status description....................................................................................................................303
Legal status end date.......................................................................................................................304
Legal status start date......................................................................................................................305
Location table........................................................................................................................................306
Facility type ......................................................................................................................................307
Location code...................................................................................................................................308
Location description .........................................................................................................................309
Occupation table ...................................................................................................................................310
Occupation code ..............................................................................................................................311
Occupation code description ............................................................................................................312
Payee table ...........................................................................................................................................313
Change flag......................................................................................................................................314
Payee DHB ......................................................................................................................................315
Payee description.............................................................................................................................316
Payee number..................................................................................................................................317
Payee perorg number.......................................................................................................................318
Perorg legal name............................................................................................................................319
Perorg name ....................................................................................................................................320
Sequence number............................................................................................................................321
Provider table........................................................................................................................................322
Current practising certificate.............................................................................................................323
Deregistration date...........................................................................................................................324
Health professional group code........................................................................................................325
Perorg first name..............................................................................................................................326
Perorg name ....................................................................................................................................327
Perorg number .................................................................................................................................328
Perorg second name........................................................................................................................329
Perorg title........................................................................................................................................330
Pharmac provider type .....................................................................................................................331
Pharmac registration number ...........................................................................................................332
Practice address 1 ...........................................................................................................................333
Practice address 2 ...........................................................................................................................334
Practice address 3 ...........................................................................................................................335
Version 2.3 MoH 7
January 2010
9. Shared Dimensions Data Dictionary Shared Dimensions
Provider DHB code ..........................................................................................................................336
Provider address ..............................................................................................................................337
Provider address 2 ...........................................................................................................................338
Provider city .....................................................................................................................................339
Provider occupation .........................................................................................................................340
Provider occupation desc .................................................................................................................341
Provider registration number ............................................................................................................342
Provider type ....................................................................................................................................343
Provider type desc ...........................................................................................................................344
Source system .................................................................................................................................345
Purchase Unit table...............................................................................................................................346
Dim purchase unit key......................................................................................................................347
End date...........................................................................................................................................348
IDF unit of measure..........................................................................................................................349
Mandatory in NNPAC .......................................................................................................................350
Purchase unit code ..........................................................................................................................351
Purchase unit description .................................................................................................................352
Purchase unit type ...........................................................................................................................353
Start date..........................................................................................................................................354
Unit of measure................................................................................................................................355
Purchaser Code table ...........................................................................................................................356
Purchaser address ...........................................................................................................................357
Purchaser code ................................................................................................................................358
Purchaser code description..............................................................................................................359
Purchaser end date..........................................................................................................................360
Purchaser start date.........................................................................................................................361
Time of day table ..................................................................................................................................362
AM / PM ...........................................................................................................................................363
Hours since midnight........................................................................................................................364
Minute of hour ..................................................................................................................................365
Minutes since midnight.....................................................................................................................366
Appendix A: Data Dictionary Template ...................................................................................................... i
Appendix B: Glossary .............................................................................................................................. iii
Appendix C: Overview of a Data Warehouse........................................................................................... iv
Appendix D: Index of Element Names ..................................................................................................... vi
Appendix E: Guide for Use of Emergency Department (ED) Event End Type Codes.............................. ix
Version 2.3 MoH 8
January 2010
10. Shared Dimensions Data Dictionary Shared Dimensions
Shared Dimensions
Purpose The purpose of the Shared Dimensions data dictionary is to record all
common dimension tables in the Oracle data warehouse.
Where a dimension is unique to a datamart, then that dimension will be
recorded as part of the primary data dictionary.
Content
Start date
Guide for use The dimensions are codes and descriptions, based on reference data.
Dimension data includes items such as Provider IDs, Health Care User
IDs, Ethnic Groups, etc.
Read this data dictionary in conjunction with the primary data dictionary,
for example, PHO Data Dictionary.
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
Frequency of updates
Security of data
Privacy 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.
In 2002 claims, the encrypted NHI number is stored for approximately
70 percent of laboratory test records. (In earlier years, it varied,
dropping to as low as 13 percent in 1997 claims.) Identifying information
is only held for health providers who request the test and not for the
pathologist performing the test.
National reports and
publications
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 2.3 MoH 9
January 2010
11. Shared Dimensions Data Dictionary Affiliation table
Affiliation table
Table name dim_affiliation
Definition This table is a matrix of gender and ethnicity code combination. Each
row denotes the gender and ethnicity combination applicable to a
person at the time of a transaction, i.e. it does not change over time.
Primary key dim_affiliation_key
Business key gender_code, ethnic_code_1, ethnic_code_2, ethnic_code_3
Guide for use The record in this table is linked to the Fact table for a transaction so
that the values of gender and ethnicity in the row in this table are the
gender and ethnicity of the Health Care User at the time the transaction
in the fact table took place.
The pointer to this record, is the value of the column dim_affiliation_key
in the fact table. This pointer in the fact table points to the record in the
dim_affiliation table with that value of the field dim_affiliation_key,
thereby exposing the combination of gender and ethnicity which is valid
for the fact table record.
Relational rules
Data content
Version 2.3 MoH 10
January 2010
12. Shared Dimensions Data Dictionary Affiliation table
Ethnic code 1
Definition A social group whose members have one or more of the following four
characteristics:
- they share a sense of common origins
- they claim a common and distinctive history and destiny
- they possess one or more dimensions of collective cultural
individuality
- they feel a sense of unique collective solidarity.
Column name ethnic_code_1
Table name dim_affiliation
Data type varchar2(2)
Other names Ethnic group
Context The first recorded ethnicity of the healthcare user.
Information on ethnicity is collected for planning and service delivery
purposes and for monitoring health status across different ethnic
groups. Ethnic group codes are key variables for determining the
characteristics of the population that are using the health sector.
Layout NN
Data domain 10 European not further defined
11 New Zealand European/Pakeha
12 Other European
21 Maori
30 Pacific Peoples not further defined
31 Samoan
32 Cook Island Maori
33 Tongan
34 Niuean
35 Tokelauan
36 Fijian
37 Other Pacific Peoples
40 Asian not further defined
41 Southeast Asian
42 Chinese
43 Indian
44 Other Asian
51 Middle Eastern
52 Latin American/Hispanic
53 African (or cultural group of African origin)
54 Other (retired 01/07/2009)
61 Other ethnicity
94 Don't know
95 Refused to answer
97 Response unidentifiable
99 Not stated
Guide for use The first recorded ethnicity of the healthcare user.
Up to 3 Ethnic group codes can be collected for each healthcare user
and each event. Where more than 3 Ethnic group codes are reported,
the Statistics NZ prioritisation algorithm is used to report only 3 values.
Code ‘54’ (Other) is retired from 01 July 2009 and should not be used
after this date. Use of the code '61' (Other Ethnicity) is limited to a very
small number of ethnic groups. It must not be used as a generic 'other'
code. If a person chooses not to answer the ethnicity question, record
their ethnicity using an appropriate residual response.
Because ethnicity is self-identified, it can change over time. This is why
Version 2.3 MoH 11
January 2010
13. Shared Dimensions Data Dictionary Affiliation table
NZHIS collects ethnicity information for each health event, rather than
relying on the data in the National Health Index (which does not include
historical data).
Verification rules
Collection methods Each ethnic group maintained by Statistics NZ has a 5-digit code.
NZHIS collections use ethnicity recorded at level 2.
Related data Prioritised ethnic code
Ethnicity code 2
Ethnicity code 3
Source document See Ethnic Group code table:
http://www.nzhis.govt.nz/moh.nsf/pagesns/47
Source organisation Statistics NZ, modified by the National Data Policy Group
Version 2.3 MoH 12
January 2010
14. Shared Dimensions Data Dictionary Affiliation table
Ethnic code 2
Definition See Ethnic code 1.
Column name ethnic_code_2
Table name dim_affiliation
Data type varchar2(2)
Other names
Context
Layout NN
Data domain 10 European not further defined
11 New Zealand European/Pakeha
12 Other European
21 Maori
30 Pacific Peoples not further defined
31 Samoan
32 Cook Island Maori
33 Tongan
34 Niuean
35 Tokelauan
36 Fijian
37 Other Pacific Peoples
40 Asian not further defined
41 Southeast Asian
42 Chinese
43 Indian
44 Other Asian
51 Middle Eastern
52 Latin American/Hispanic
53 African (or cultural group of African origin)
54 Other (retired 01/07/2009)
61 Other ethnicity
94 Don't know
95 Refused to answer
97 Response unidentifiable
99 Not stated
Guide for use The second recorded ethnicity of the healthcare user.
Verification rules
Collection methods
Related data Prioritised ethnic code
Ethnicity code 1
Ethnicity code 3
Source document
Source organisation
Version 2.3 MoH 13
January 2010
15. Shared Dimensions Data Dictionary Affiliation table
Ethnic code 3
Definition See Ethnic code 1.
Column name ethnic_code_3
Table name dim_affiliation
Data type varchar2(2)
Other names
Context
Layout NN
Data domain 10 European not further defined
11 New Zealand European/Pakeha
12 Other European
21 Maori
30 Pacific Peoples not further defined
31 Samoan
32 Cook Island Maori
33 Tongan
34 Niuean
35 Tokelauan
36 Fijian
37 Other Pacific Peoples
40 Asian not further defined
41 Southeast Asian
42 Chinese
43 Indian
44 Other Asian
51 Middle Eastern
52 Latin American/Hispanic
53 African (or cultural group of African origin)
54 Other (retired 01/07/2009)
61 Other ethnicity
94 Don't know
95 Refused to answer
97 Response unidentifiable
99 Not stated
Guide for use The third recorded ethnicity of the healthcare user.
Verification rules
Collection methods
Related data Prioritised ethnic code
Ethnicity code 1
Ethnicity code 2
Source document
Source organisation
Version 2.3 MoH 14
January 2010
16. Shared Dimensions Data Dictionary Affiliation table
Ethnicity 1
Definition A description of the ethnic code 1
Column name ethnicity_1
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout Free text
Data domain
Guide for use The description of the first recorded ethnicity.
Verification rules
Collection methods
Related data Ethnicity code 1
Ethnicity 2
Ethnicity 3
Source document
Source organisation
Version 2.3 MoH 15
January 2010
17. Shared Dimensions Data Dictionary Affiliation table
Ethnicity 2
Definition See Ethnicity 1.
Column name ethnicity_2
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout Free text
Data domain
Guide for use The description of the second recorded ethnicity.
Verification rules
Collection methods
Related data Ethnicity code 2
Ethnicity 1
Ethnicity 3
Source document
Source organisation
Version 2.3 MoH 16
January 2010
18. Shared Dimensions Data Dictionary Affiliation table
Ethnicity 3
Definition See Ethnicity 1.
Column name ethnicity_3
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout Free text
Data domain
Guide for use The description of the third recorded ethnicity.
Verification rules
Collection methods
Related data Ethnicity code 3
Ethnicity 1
Ethnicity 2
Source document
Source organisation
Version 2.3 MoH 17
January 2010
19. Shared Dimensions Data Dictionary Affiliation table
Gender
Definition The individual's gender is either male, female or unknown. An
individual with an 'unknown' gender will be assigned the male value.
Column name gender
Table name dim_affiliation
Data type varchar2(30)
Other names
Context
Layout Free Text
Data domain
Guide for use
Verification rules
Collection methods
Related data Gender Code
Source document
Source organisation
Version 2.3 MoH 18
January 2010
20. Shared Dimensions Data Dictionary Affiliation table
Gender Code
Definition The individual's biological sex.
Column name gender_code
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout A
Data domain M Male
F Female
U Unknown
I Indeterminate
Guide for use Within the CBF Extract only 'M' and 'F' are used. 'U' and 'I' are
converted to 'M' during HealthPAC processing.
Verification rules
Collection methods
Related data Gender
Source document
Source organisation
Version 2.3 MoH 19
January 2010
21. Shared Dimensions Data Dictionary Affiliation table
Level 0 ethnic code 1
Definition This is the level 0 code of the first of the three ethnic groups recorded
for the patient (healthcare user).
Column name level_0_ethnic_code_1
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout
Data domain Level 0 ethnicity is a hierarchical classification with 3 levels.
2 Maori
3 Pacific Island
6 Other
Guide for use This is the first recorded ethnicity at level 0, i.e. Ethnic Code 1 - Level 0
Ethnic Code 1
Verification rules
Collection methods
Related data level_0_ethnicity_1
Source document
Source organisation
Version 2.3 MoH 20
January 2010
22. Shared Dimensions Data Dictionary Affiliation table
Level 0 ethnic code 2
Definition See Level 0 Ethnic code 1.
Column name level_0_ethnic_code_2
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout
Data domain
Guide for use This is the second recorded ethnicity at level 0, i.e. Ethnic Code 2 -
Level 0 Ethnic Code 2
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 21
January 2010
23. Shared Dimensions Data Dictionary Affiliation table
Level 0 ethnic code 3
Definition See Level 0 Ethnic code 1.
Column name level_0_ethnic_code_3
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout
Data domain
Guide for use This is the third recorded ethnicity at level 0, i.e. Ethnic Code 3 - Level
0 Ethnic Code 3
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 22
January 2010
24. Shared Dimensions Data Dictionary Affiliation table
Level 0 ethnicity 1
Definition This is the level 0 description of the first of the three ethnic groups
recorded for the patient (healthcare user).
Column name level_0_ethnicity_1
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout
Data domain 2 Maori
3 Pacific Island
6 Other
Guide for use This is the description of the first recorded ethnicity at level 0.
Verification rules
Collection methods
Related data level_0_ethnic_code_1
Source document
Source organisation
Version 2.3 MoH 23
January 2010
25. Shared Dimensions Data Dictionary Affiliation table
Level 0 ethnicity 2
Definition See Level 0 Ethnic 1.
Column name level_0_ethnicity_2
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout
Data domain
Guide for use This is the description of the second recorded ethnicity at level 0.
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 24
January 2010
26. Shared Dimensions Data Dictionary Affiliation table
Level 0 ethnicity 3
Definition See Level 0 Ethnic 1.
Column name level_0_ethnicity_3
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout
Data domain
Guide for use This is the description of the third recorded ethnicity at level 0.
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 25
January 2010
27. Shared Dimensions Data Dictionary Affiliation table
Level 1 ethnic code 1
Definition This is the level 1 code of the first of the three ethnic groups recorded
for the patient (healthcare user).
Column name level_1_ethnic_code_1
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout
Data domain Level one has 7 categories -
1 European
2 Maori
3 Pacific Island
4 Asian
5 MELAA
6 Other
9 Unspecified
Guide for use This is the first recorded ethnicity at level 1, i.e. Ethnic Code 1 - Level
1 Ethnic Code 1
Verification rules
Collection methods
Related data level_1_ethnicity_1
Source document
Source organisation
Version 2.3 MoH 26
January 2010
28. Shared Dimensions Data Dictionary Affiliation table
Level 1 ethnic code 2
Definition See Level 1 Ethnic code 1.
Column name level_1_ethnic_code_2
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout
Data domain
Guide for use This is the second recorded ethnicity at level 1, i.e. Ethnic Code 2 -
Level 1 Ethnic Code 2
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 27
January 2010
29. Shared Dimensions Data Dictionary Affiliation table
Level 1 ethnic code 3
Definition See Level 1 Ethnic code 1.
Column name level_1_ethnic_code_3
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout
Data domain
Guide for use This is the third recorded ethnicity at level 1, i.e. Ethnic Code 3 - Level
1 Ethnic Code 3
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 28
January 2010
30. Shared Dimensions Data Dictionary Affiliation table
Level 1 ethnicity 1
Definition This is the level 1 description of the first of the three ethnic groups
recorded for the patient (healthcare user).
Column name level_1_ethnicity_1
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout
Data domain 1 European
2 Maori
3 Pacific Island
4 Asian
5 MELAA
6 Other
9 Unspecified
Guide for use This is the description of the first recorded ethnicity at level 1.
Verification rules
Collection methods
Related data level_1_ethnic_code_1
Source document
Source organisation
Version 2.3 MoH 29
January 2010
31. Shared Dimensions Data Dictionary Affiliation table
Level 1 ethnicity 2
Definition See Level 1 Ethnic 1.
Column name level_1_ethnicity_2
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout
Data domain
Guide for use This is the description of the second recorded ethnicity at level 1.
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 30
January 2010
32. Shared Dimensions Data Dictionary Affiliation table
Level 1 ethnicity 3
Definition See Level 1 Ethnic 1.
Column name level_1_ethnicity_3
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout
Data domain
Guide for use This is the description of the third recorded ethnicity at level 1.
Verification rules
Collection methods
Related data
Source document
Source organisation
Version 2.3 MoH 31
January 2010
33. Shared Dimensions Data Dictionary Affiliation table
Priority ethnicity
Definition A description of the most highly prioritised ethnicity of the three ethnic
groups recorded for the healthcare user, determined according to a
Statistics NZ algorithm.
Column name priority_ethnicity
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout Free Text
Data domain 10 European not further defined
11 New Zealand European/Pakeha
12 Other European
21 Maori
30 Pacific Peoples not further defined
31 Samoan
32 Cook Island Maori
33 Tongan
34 Niuean
35 Tokelauan
36 Fijian
37 Other Pacific Peoples
40 Asian not further defined
41 Southeast Asian
42 Chinese
43 Indian
44 Other Asian
51 Middle Eastern
52 Latin American/Hispanic
53 African (or cultural group of African origin)
54 Other (retired 01/07/2009)
61 Other ethnicity
94 Don't know
95 Refused to answer
97 Response unidentifiable
99 Not stated
Guide for use
Verification rules
Collection methods
Related data Related to the priority ethnic code field in the Health Care User table
Source document
Source organisation
Version 2.3 MoH 32
January 2010
34. Shared Dimensions Data Dictionary Affiliation table
Priority ethnicity code
Definition The most highly prioritised ethnicity of the three ethnic groups recorded
for the healthcare user, determined according to a Statistics NZ
algorithm.
Column name priority_ethnic_code
Table name dim_affiliation
Data type varchar2(2)
Other names
Context
Layout NN
Data domain See the Ethnicity code table on the NZHIS web site at
http://www.nzhis.govt.nz/moh.nsf/pagesns/47. 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 Ethnic codes are ranked on the Ethnicity code table from '1' (highest
priority) to '22' (lowest priority), with '94' for 'Don't Know', '95' for
'Refused to Answer', '97' for 'Response Unidentifiable' and '99' for 'Not
stated'. Prioritised ethnic code is the healthcare user's ethnic code with
the highest priority. Prioritising ethnic codes simplifies analysis.
Verification rules
Collection methods
Related data prioritised_ethnicity
Ethnic_group_code
Source document
Source organisation
Version 2.3 MoH 33
January 2010
35. Shared Dimensions Data Dictionary Affiliation table
level 0 priority ethnic code
Definition This is the level 0 code of the most highly prioritised ethnicity of the
three ethnic groups recorded for the patient (healthcare user),
determined according to a Statistics NZ algorithm. At this level,
ethnicities from level 1 are rolled up into three into three main ethnic
groups.
Level 0 groups ethnicities into: '2' (represents Maori), '3' (represents
Pacific peoples), '6' (represents Other)
Column name level_0_priority_ethnic_code
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout AA
Data domain 2 Maori
3 Pacific Island
6 Other
Guide for use This field is derived from the Prioritised ethnic code and the Level 0
ethnic code.
Verification rules
Collection methods
Related data level_0_priority_ethnicity
Source document
Source organisation
Version 2.3 MoH 34
January 2010
36. Shared Dimensions Data Dictionary Affiliation table
level 0 priority ethnicity
Definition This is the level 0 description of the most highly prioritised ethnicity of
the three ethnic groups recorded for the patient (healthcare user),
determined according to a Statistics NZ algorithm.
Level 0 groups ethnicities into: 'Maori', 'Pacific Island', 'Other'.
Column name level_0_priority_ethnicity
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout Free text
Data domain 2 Maori
3 Pacific Island
6 Other
Guide for use This is the description of the prioritised ethnicity at level 0.
Verification rules
Collection methods
Related data level_0_priority_ethnic_code
Source document
Source organisation
Version 2.3 MoH 35
January 2010
37. Shared Dimensions Data Dictionary Affiliation table
level 1 priority ethnic code
Definition This is the level 1 code of the most highly prioritised ethnicity of the
three ethnic groups recorded for the patient (healthcare user),
determined according to a Statistics NZ algorithm.
Level 1 groups ethnicities into: '1' (European), '2' (Maori), '3' (Pacific
Island), '4' (Asian), '5' (MELAA), '6' (Other), '9' (Unspecified).
Column name level_1_priority_ethnic_code
Table name dim_affiliation
Data type char(1)
Other names
Context
Layout AA
Data domain 1 European
2 Maori
3 Pacific Island
4 Asian
5 MELAA
6 Other
9 Unspecified
Guide for use This field is derived from the Prioritised ethnic code and the Level 1
ethnic code.
Verification rules
Collection methods
Related data level_1_priority_ethnicity
Source document
Source organisation
Version 2.3 MoH 36
January 2010
38. Shared Dimensions Data Dictionary Affiliation table
level 1 priority ethnicity
Definition This is the level 1 description of the most highly prioritised ethnicity of
the three ethnic groups recorded for the patient (healthcare user),
determined according to a Statistics NZ algorithm.
Level 1 groups ethnicities into: European, Maori, Pacific Island, Asian,
MELAA, Other, Unspecified.
Column name level_1_priority_ethnicity
Table name dim_affiliation
Data type varchar2(50)
Other names
Context
Layout Free text
Data domain 1 European
2 Maori
3 Pacific Island
4 Asian
5 MELAA
6 Other
9 Unspecified
Guide for use This is the description of the prioritised ethnicity at level 1.
Verification rules
Collection methods
Related data level_1_priority_ethnic_code
Source document
Source organisation
Version 2.3 MoH 37
January 2010
39. Shared Dimensions Data Dictionary Age Band table
Age Band table
Table name dim_age_band
Definition This dimension table contains a record for each age from 0 to 115
years. The ages are also grouped into 5 and 10 year age bands, the
GMS age bands and the PHO CBF Bands
Primary key dim_age_band_key
Business key age_in_years
Guide for use The table is prepopulated with age records.
Each fact table record will point to the record in the age band table,
which contains the age of the Health Care User at the time of the
transaction. This is calculated during the load of the fact table from the
Health Care Users date of birth and the transaction date.
The age band columns in the dim_age_band dimension can be
selected directly into queries, providing the analyst with age banded
groupings for counts and totals, without having to perform their own
grouping.
If there is no NHI Number, the age will be undefined.
Relational rules This dimension is shared between a number of datamarts.
Data content
Version 2.3 MoH 38
January 2010