HEALTH NFORMATION STANDARDS COMMITTEE FOR ALBERTA€¦ · 3.1 2014-Mar-03 • Updates to various descriptions • Updates to permissible values 3.5 2018-Aug-27 Amendment: ... 101

Health Information Data Standard

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA

NEWBORN METABOLIC SCREENING DATA SET

Status: Approved Version: 3.5 Status Date: 2018-Aug-27

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA NEWBORN METABOLIC SCREENING DATA SET 2018-AUG-27

© 2018 Government of Alberta 2 of 135

Revision History Version Version Date Summary of Changes

0.0 2000-Feb-16 Accepted in Draft 1.0 2003-Dec-04 Approved 2.0 2009-Sep-09 Amendment created due to major changes to the NMS application 2.1 2010-Mar-10 Amendment to add 3 new data elements 3.0 2013-Mar-03 Amendment:

• Changed compound name/entity from Reconciliation Alert Informationto Alert Action Information

• Moved data element Parent Postal Code from compound name/entityParent Contact Information to Address

• Changes on data elements of Newborn compound name/entity:o removed Birth RHA, Responsible RHA, Residence RHAo removed Birth District, Responsible Districto added Birth Zone, Responsible Zoneo added Newborn Flag, Registered Flag, Birth Counto updated Birth Order size to align with standard

• Changes on data elements of Newborn Transfer compoundname/entity:o removed Initiate RHA, Destination RHAo removed Initiate RHA comment, Destination RHA commento added Initiate Zone District, Destination Zone Districto added Initiate Zone District Comment, Destination Zone District

Comment• Changes on data elements of Lab Order compound name/entity:

o removed Placer Order Number, Region Submitting Sampleo added Zone of Collection, Lab Newborn Gender

• Updates to various descriptions• Updates to permissible values

3.1 2014-Mar-03 • Updates to various descriptions• Updates to permissible values

3.5 2018-Aug-27 Amendment: • Added Birth Weight and Gestational Age data elements• Added Masked Flag element to Newborn• Added Extension element to Referral• Updated Permissible values• Added Implementation Consideration for Action reason, Lab Test Alert

End Reason, and Newborn Alert End Reason

HISCA status: Approved on September 11, 2018



Table of Contents I. Introduction ...................................................................................................................................... 6 II. Background ...................................................................................................................................... 6

Business Case for the health system ............................................................................................... 6 Impact on privacy, confidentiality and security................................................................................. 6 Relationship to existing standards and/or legislation ....................................................................... 7

III. Conceptual Data Model.................................................................................................................... 8 IV. Logical Data Model .......................................................................................................................... 9 V. Data Standards .............................................................................................................................. 10

Newborn Metabolic Screening ......................................................................................................... 10 Newborn ...................................................................................................................................................... 11

Newborn ULI .................................................................................................................................... 12 Newborn Surname ........................................................................................................................... 13 Newborn First Given Name .............................................................................................................. 14 Newborn Other Given Name ............................................................................................................ 15 Newborn Gender .............................................................................................................................. 16 Newborn Birth Date .......................................................................................................................... 17 Newborn Flag ................................................................................................................................... 18 Registered Flag ................................................................................................................................ 19 Birth Zone ......................................................................................................................................... 20 Responsible Zone ............................................................................................................................ 21 Residence Zone ............................................................................................................................... 22 Special Status .................................................................................................................................. 23 Birth Order ........................................................................................................................................ 24 Birth Count ....................................................................................................................................... 25 PD Registration Date Time .............................................................................................................. 26 Newborn End Date ........................................................................................................................... 27 Newborn End Reason Code ............................................................................................................ 28 Masked Flag ..................................................................................................................................... 29

Parent Contact Information ......................................................................................................................... 30 Parent ULI ........................................................................................................................................ 31 Parent Surname ............................................................................................................................... 32 Parent First Given Name .................................................................................................................. 33 Parent ULI Not Available Reason Code ........................................................................................... 34

Telephone ................................................................................................................................................... 35 Home Phone Area Code .................................................................................................................. 36 Home Phone Number....................................................................................................................... 37 Phone Silent Indicator ...................................................................................................................... 38

Birth Delivery Site ........................................................................................................................................ 39 Facility Identifier ............................................................................................................................... 40 Facility Name .................................................................................................................................... 41

Address ....................................................................................................................................................... 42 Address Line 1 ................................................................................................................................. 43 Address Line 2 ................................................................................................................................. 44 Address Line 3 ................................................................................................................................. 45 City Name ......................................................................................................................................... 46 Province State Code ........................................................................................................................ 47 Country Code ................................................................................................................................... 48 Postal Code ...................................................................................................................................... 49 Bad Address Indicator ...................................................................................................................... 50 Temporary Address Indicator ........................................................................................................... 51

Newborn Transfer ....................................................................................................................................... 52 Initiate Zone District .......................................................................................................................... 53 Destination Zone District .................................................................................................................. 54 Transfer Start Date ........................................................................................................................... 55 Transfer Resolved Date ................................................................................................................... 56



Transfer Status ................................................................................................................................. 57 Initiate Zone District Comment ......................................................................................................... 58 Destination Zone District Comment ................................................................................................. 59

Newborn Alert ............................................................................................................................................. 60 Newborn Alert Date .......................................................................................................................... 61 Alert Code ........................................................................................................................................ 62 Newborn Escalation Date ................................................................................................................. 63 Newborn Alert End Reason .............................................................................................................. 64

Lab Order .................................................................................................................................................... 65 Zone of Collection ............................................................................................................................ 66 Accession Number ........................................................................................................................... 67 Message Date Time ......................................................................................................................... 68 Lab Newborn Gender ....................................................................................................................... 69 Lab Newborn Birth Date ................................................................................................................... 70 Lab Newborn Birth Time .................................................................................................................. 71 Comments ........................................................................................................................................ 72 Order Control Reason ...................................................................................................................... 73 Record End Reason Code ............................................................................................................... 74 Birth Weight ...................................................................................................................................... 75 Gestational Age ................................................................................................................................ 76 Lab Test Result ................................................................................................................................ 77

Test Result Value ......................................................................................................................... 78 Test Result Test ............................................................................................................................ 79

Test Type code ........................................................................................................................ 80 Test Description ...................................................................................................................... 81

Specimen Collection Information ..................................................................................................... 82 Collector Identifier ......................................................................................................................... 83 Collection Date Time .................................................................................................................... 84 Specimen Received Date Time .................................................................................................... 85 Specimen Collection Site .............................................................................................................. 86

Collection Location Identifier ................................................................................................... 87 Lab Test Alert .............................................................................................................................................. 88

Lab Test Alert Date .......................................................................................................................... 89 Alert Code ........................................................................................................................................ 90 Lab Test Escalation Date ................................................................................................................. 91 Lab Test Alert End Reason .............................................................................................................. 92

Lab Order Alert ............................................................................................................................................ 93 Lab Order Alert Date ........................................................................................................................ 94 Alert Code ........................................................................................................................................ 95 Lab Order Alert End Reason ............................................................................................................ 96 Alert Action Information .................................................................................................................... 97

Action Alert Date ........................................................................................................................... 98 Action Taken ................................................................................................................................. 99 Action Comment ......................................................................................................................... 100 Action Reason ............................................................................................................................ 101 Referral ....................................................................................................................................... 102

Full Name From ..................................................................................................................... 103 Full Name To ......................................................................................................................... 104 Phone Number ...................................................................................................................... 105 Extension ............................................................................................................................... 106 FAX Flag................................................................................................................................ 107 Referral Date ......................................................................................................................... 108

Alert Code ................................................................................................................................................. 109 Alert Code ...................................................................................................................................... 110 Subclass Indicator .......................................................................................................................... 111 Short Description ............................................................................................................................ 112 Long Description ............................................................................................................................ 113 Escalate Flag .................................................................................................................................. 114



Escalate Number of Days .............................................................................................................. 115 Birth Date Escalation Flag .............................................................................................................. 116 First Alert Number of Days ............................................................................................................. 117

VI. Permissible Values ....................................................................................................................... 118 Newborn Gender .......................................................................................................................... 118 Birth Zone ..................................................................................................................................... 118 Responsible Zone ........................................................................................................................ 119 Residence Zone ........................................................................................................................... 119 Birth Order .................................................................................................................................... 120 Newborn End Reason Code ........................................................................................................ 120 Parent ULI Not Available Reason Code ....................................................................................... 120 Province State Code .................................................................................................................... 121 Initiate Zone District ..................................................................................................................... 123 Destination Zone District .............................................................................................................. 124 Newborn Alert End Reason ......................................................................................................... 125 Zone of Collection ........................................................................................................................ 126 Lab Newborn Gender ................................................................................................................... 126 Record End Reason Code ........................................................................................................... 126 Test Type Code ............................................................................................................................ 127 Lab Test Alert End Reason .......................................................................................................... 128 Lab Order Alert End Reason ........................................................................................................ 128 Action Taken ................................................................................................................................ 129 Action Reason .............................................................................................................................. 130 Subclass Indicator ........................................................................................................................ 132 Alert Code - N codes (Alert-Interpretation Codes) ....................................................................... 133 Alert Code – Non-N codes (Alert-Interpretation Codes) .............................................................. 135



I. Introduction The purpose of this document is to define the data set for the operation of the Newborn Metabolic Screening (NMS) Program in the province of Alberta. The elements included in the data set are related to an infant’s demographics, birth record, laboratory record and information collected during the screening pathway (registration, collection and transportation, analysis and reporting, follow-up).

II. Background The NMS Program is a population based screening program that provides newborn blood spot screening to all infants born in Alberta. Infants born outside Alberta and receiving health care in Alberta may also be screened. Infants are screened for conditions that can lead to severe physical disabilities, developmental delay, other health problems or even death. Morbidity and mortality of Alberta infants with the screened conditions is minimized through timely and effective screening to allow early diagnosis and treatment of affected infants.

The program is delivered by Alberta Health Services (AHS) in partnership with Alberta Health, Health Canada - First Nations Inuit Health Branch Alberta Region (FNIHB), providers, and parents and guardians.

Alberta Health sets the policies and standards for the program, determines the list of screened conditions, monitors compliance with policy, and maintains the NMS Application - a secure, web-based application that reconciles registered births and newborn blood spot screen results and generates alerts which assist in identifying and tracking of infants requiring follow-up. Data collected in the NMS Application is also used by AHS and Alberta Health to monitor program performance measures.

The 2010 Alberta Newborn Metabolic Screening Program Policy Document sets out program policies and roles and responsibilities for implementing the NMS Program. The program policy is located here - Newborn Metabolic Screening Program Documents.

Business Case for the health system

One of the goals of the NMS Program is to ensure that all babies born in Alberta have timely access to newborn blood spot screening as an integral component of their health care.

The Newborn Metabolic Screening Application allows the following:

• Secure access for authorized users to track registered births and status of screening. • A mechanism for the transfer of responsibility between AHS and FNIHB • Tracking of quality indicators and performance measures • Public health surveillance activities.

Impact on privacy, confidentiality and security

The Newborn Metabolic Screening (NMS) System Privacy Impact Assessment was submitted by Alberta We//net to the Office of the Information and Privacy Commissioner (OIPC) and received OIPC

http://www.health.alberta.ca/professionals/newborn-metabolic-screening.html



acceptance on March 21, 2001. An addendum was submitted in July, 2001 to address changes introduced by the proclamation of the Health Information Act (HIA), as well as the need for access to the information for the purpose of conducting health system surveillance. Alberta Health and Wellness submitted the second NMS PIA April 30, 2007 to replace the 2001 PIA and addendum. In August 2008, the OIPC provided their acceptance on the revisions made to the PIA. The PIA was refreshed by Alberta Health in February 2011 and accepted by the OIPC in 2012. An addendum to this PIA was accepted by the OIPC in June 2013. It addressed a change which integrates the use of Provincial Client Registry Web Services (PCR-WS) as an additional source for client information in the NMS Application. A second addendum was submitted in August 2014 to address a change in the mechanism by which information is shared between the Public Health Team at FNIHB, AHS and Alberta Health. The OIPC provided their acceptance on the revisions on January 2015. On June 2017, addendum 3 was submitted to address the collection of two additional data elements from NMS Laboratory: birth weight and gestational age. OIPC accepted this change on August 2017.

Relationship to existing standards and/or legislation

As the information requirements of the NMS Application were identified during development, the existing HISCA standards, Stakeholder Basic Demographic Standard and Service Event Data Model, were used to align the NMS minimum data set. During 2013 updates, a standards alignment review was completed against Stakeholder Basic Demographic Standard and Lab Test Results Delivery Message Standard. Note: At this time, the Lab and NMS application are not compliant with HL7 Messaging Standard v2.3, which provides 200 characters as a normative limit for ORC-16.

In the HISCA Laboratory Test Results Delivery (LTRD) Message Specification document, version 2.1, the length of ORC-16 (Order Code Reason) is defined as 80 characters. ORC 16.1 (Code) and ORC 16.2 (Description) are defined as 20 characters and 60 characters respectively. The 16.1 Code and 16.2 Description data elements were not noted in the HL7 v2.3 documentation which implies that 16.1 and 16.2 are add-ons for Alberta for additional data. The Lab and NMS application are not compliant with HISCA LTRD v 2.1 for ORC-16 or ORC 16.2



III. Conceptual Data Model A conceptual data model is the first step in expressing a data model at an enterprise level (AHEAD – Alberta Health Enterprise Architecture Definition) and is a clear visual representation of the business within the scope of the project. It provides/scopes high-level information about the subject areas of an organization in a way which is not governed by implementation-level issues and details.

Governance

Jurisdiction

Program

Event

Administrative Event

Stakeholder In A Role

Administrative Intervention Event

Service

Clinical Service

Boundary

Health Monitor / Surveillance EventService Event

Communication Event

Notification Event

Is A

Consumes/Provides

Involves

Participates in

Provider Organization

Health Delivery Organization

Recipient Recipient Contact

Can be contacted using

Contains

Funds/Mandates

Physical Address

Canadian Address

Is physical located at

Operates/Runs/Responsible

Health Care Visit Event

Referral Event

Affects

Service/Event SiteRelates To

Communication Access

Telecom

Disease Control and Prevention

Delivery Site

Facility

Entity – defines a collection of stored data

Legend

One or More

Zero or more

One only

Stakeholder

Person

Group

Organization

Diagnostic Service Event

Can be contacted using

Relates to

Relates to

Newborn Metabolic Screening

Scene

Home Birth

Entity source of truth, PD & LIS

Newborn Transfer



IV. Logical Data Model

Newborn

Newborn ULI Newborn Surname Newborn First Given Name Newborn Other Given Name Newborn Gender Newborn Birth Date Newborn Flag Registered Flag Birth Zone Responsible Zone Residence Zone Special Status Birth Order Birth Count PD Registration Date Time Newborn End Date Newborn End Reason Code Masked Flag

Birth Delivery Site

Facility Identifier Facility Name

Attribute Names in Bold lettering are business key(s).

Legend

Entity – defines a collection of stored data

Relationship – describes how two Entities relate to one another

© 2017 Government of Alberta

Alberta Health Version 3.1.1Newborn Metabolic Screening Logical Data Model Date: 2018-08-28

Parent Contact Information

Parent ULI Parent Surname Parent First Given Name Parent ULI Not Available Reason Code

parent by

Lab Order

Zone of Collection Accession Number Message Date Time Lab Newborn Gender Lab Newborn Birth Date Lab Newborn Birth Time Comments Order Control Reason Record End Reason Code Birth Weight Gestational Age

has

Lab Test Result

Test Result Value

has

Specimen Collection Information

Collector Identifier Collection Date Time Specimen Received Date Time

has

Specimen Collection Site

Collection Location Identifier

taken at

Lab Test Alert

Lab Test Alert Date Alert Code Lab Test Escalation Date Lab Test Alert End Reason

raise

Alert Code

Alert Code Subclass Indicator Short Description Long Description Escalate Flag Escalate Number of Days Birth Date Escalation Flag First Alert Number of Days

Referral

Full Name From Full Name To Phone Number Extension FAX Flag Referral Date

has

Test Result Test

Test Type Code Test Description

has

Alert Action Information

Action Alert Date Action Taken Action Comment Action Reason

Address

Address Line 1 Address Line 2 Address Line 3 City Name Province State Code Country Code Postal Code Bad Address Indicator Temporary Address Indicator

located by

Telephone

Home Phone Area Code Home Phone Number Phone Silent Indicator

has

raises

has

Newborn Alert

Newborn Alert Date Alert Code Newborn Escalation Date Newborn Alert End Reason

has

Lab Order Alert

Lab Order Alert Date Alert Code Lab Order Alert End Reason

has has

Newborn Transfer

Initiate Zone District Destination Zone District Transfer Start Date Transfer Resolved Date Transfer Status Initiate Zone District Comment Destination Zone District Comment

has

located at



V. Data Standards Compound Name Newborn Metabolic Screening

Parent Compound Name

Component Name Newborn

Alert Code

Submission Newborn Metabolic Screening

Requirement for the Standard

Obligation

Cardinality

Submitting Organization Alberta Health

Standard Reference

Definition Newborn Metabolic Screening (NMS) is a population based preventive health activity, which allows the early detection of a number of inherited and congenital conditions before they manifest clinically. If effective treatment is started early, these conditions are compatible with a normal lifestyle. Although the prevalence of these conditions is low, if left untreated, the cost to the individual and to the health care services delivery system can be substantial.

Business Rule/Coding Guideline



Compound Name Newborn

Parent Compound Name Newborn Metabolic Screening

Component Name



Obligation

Cardinality


Standard Reference

Definition Demographic information regarding the newborn recorded at the time the newborn is registered or as updated within 90 days. Information may also be captured from the demographics provided on the screens sent by the NMS Lab.

Business Rule/Coding Guideline A newborn can only have one Birth Event, unless it has more than one ULI. When more than one ULI exists for a newborn, a merge should take place in Person Directory/Central Stakeholder Registry.



Data Element Name Newborn ULI



Requirement for the Standard The ULI identifies the Newborn to the newborn metabolic screening application.


Standard Reference Stakeholder Basic Demographic

Definition The ULI (Unique Lifetime Identifier) is a unique and permanent number assigned to all persons of interest to the health system of Alberta. This includes Alberta residents and residents of other provinces who receive health services in Alberta.

Stakeholder-PERSON - a human being, alive or not, of interest to the health system.

Information Exchange Format Type

Num

Information Exchange Length 9

Information Exchange Format Mask

999999999

Obligation M

Cardinality 1:1

Business Rule / Coding Guideline

Implementation Consideration Check digit routine available but not utilized by NMS.

Person Directory will only assign ULIs that pass the check-digit algorithm.

Temporary identifiers (HDP#) may also be received from the laboratory information system.

Permissible Data Element Value

HISCA Alias Unique Lifetime Identifier



Data Element Name Newborn Surname



Requirement for the Standard Helps towards recognizing the unique existence of a Newborn.



Definition The full surname or family name of the Newborn


Char



Obligation M

Cardinality 1:1


Implementation Consideration The database currently supports 50 chars and is compliant with the standard.


HISCA Alias Last Name



Data Element Name Newborn First Given Name






Definition The first name of the Newborn.


Char



Obligation O

Cardinality 0:1




HISCA Alias Given Name



Data Element Name Newborn Other Given Name






Definition The other given name of a person


Char



Obligation O

Cardinality 0:1




HISCA Alias Middle Name



Data Element Name Newborn Gender






Definition For purposes of identification, the gender, as declared by the individual is captured. Gender refers to social or cultural categories, while the sex of an individual references biological categories.


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline The NMS batch process does not validate the gender. However, if the value is not one of the valid values (‘M’, ‘F’, ‘U’, ‘O’), then the batch will fail due to a database constraint violation.

Implementation Consideration The newborn's gender in the demographic section is populated by Central Stakeholder Registry (CSR) if there is a birth event received. If only a Lab Information System (LIS) file has been received, then that Gender is populated in the demographic section and under the lab information.

Permissible Data Element Value See Permissible Values

HISCA Alias Administrative Gender



Data Element Name Newborn Birth Date






Definition The calendar date on which the Newborn was born.


Date



YYYYMMDD

Obligation M

Cardinality 1:1


Implementation Consideration


HISCA Alias Birth Date



Data Element Name Newborn Flag





Standard Reference

Definition Flag indicates whether ULI was registered as a newborn ULI or as a non-newborn ULI. A newborn ULI refers to a type of ULI that is assigned using a special function when the infant is 28 days or younger and born in Alberta.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline If "1", the ULI was registered as a newborn. If "0", the ULI was registered as a non-newborn.


Permissible Data Element Value 1 = newborn.

0 = non-newborn.

HISCA Alias



Data Element Name Registered Flag





Standard Reference

Definition Flag indicates whether the individual will be considered (and counted) as a registered newborn in NMS. A registered newborn means an infant born in Alberta and assigned a newborn ULI.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline The value will be “1” if the individual is assigned a newborn ULI (newborn flag is “1”) and “0” if the individual is assigned a non-newborn ULI (newborn flag is “0”). If the individual has more than one ULI, the value will be “1” if at least one of the assigned ULIs is a newborn ULI, otherwise the value will be “0”.


Permissible Data Element Value 1 = registered.

0 = not registered.

HISCA Alias



Data Element Name Birth Zone





Standard Reference

Definition The zone where the birth took place.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline The value is determined based on the birth/registration facility. Each facility is associated to a zone, which is used as the birth zone.



HISCA Alias



Data Element Name Responsible Zone





Standard Reference

Definition The zone responsible for the follow up of the newborn.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline The initial value is set based on the zone of residence but through transfers, can be updated. For instance, when a newborn is transferred, the destination zone becomes the responsible zone.

Implementation Consideration By default, the value is the residence zone.


HISCA Alias



Data Element Name Residence Zone





Standard Reference

Definition The zone in which the newborn resides.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline The value is determined based on the newborn's mailing address postal code received from CSR. Each Alberta postal code is associated to a zone, which is used as the residence zone.



HISCA Alias



Data Element Name Special Status





Standard Reference

Definition Specifies any special status for the newborn, such as for Stillborn.


Char



Obligation O

Cardinality 0:1



Permissible Data Element Value Null,

‘NB’ indicates newborn;

‘OPNB’ indicates Out of Province Newborn;

‘STBN’ indicates Stillborn.

HISCA Alias



Data Element Name Birth Order



Requirement for the Standard Perinatal statistics: required to analyse pregnancy outcome according to birth order and identify the individual baby resulting from a multiple birth pregnancy. Multiple births have higher risks of perinatal mortality and morbidity. Multiple birth pregnancies are often associated with obstetric complications, labour and delivery complications, higher rates of neonatal morbidity, low birth weight, and a higher perinatal death rate.


Standard Reference Stakeholder - Client v1.3

Definition The birth order of this person if multiple births occurred.

For NMS, the definition reflects the birth order from a single pregnancy so the number may be 1 or greater in the case of multiple births from a single pregnancy.


Num



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Birth order is received only for newborn ULIs.



HISCA Alias



Data Element Name Birth Count



Requirement for the Standard Perinatal statistics: required to analyse pregnancy outcome according to birth order and identify the individual baby resulting from a multiple birth pregnancy. Multiple births have higher risks of perinatal mortality and morbidity. Multiple birth pregnancies are often associated with obstetric complications, labour and delivery complications, higher rates of neonatal morbidity, low birth weight, and a higher perinatal death rate.


Standard Reference Stakeholder - Client v1.3

Definition The total number of births that occurred.

For NMS, the definition reflects the birth count from a single pregnancy so the number may be 1 or greater in the case of multiple births from a single pregnancy.


Num



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Birth count is received only for newborn ULIs.


Permissible Data Element Value Null, 1 to 9

HISCA Alias



Data Element Name PD Registration Date Time





Standard Reference

Definition Date and time that the newborn’s record was created in Person Directory.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Newborn End Date



Requirement for the Standard Required for neonatal deaths or records that were added in error.


Standard Reference

Definition The date the stakeholder record was ended.


Date



YYYYMMDD

Obligation C

Cardinality 0:1

Business Rule / Coding Guideline This is required when Newborn End Reason code is specified.



HISCA Alias Death Date (when Newborn End Reason Code = DECD)



Data Element Name Newborn End Reason Code





Standard Reference

Definition This field specifies the reason why the newborn’s record was ended.


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline This is required when Newborn End date is specified.

Implementation Consideration “DECD” indicates that the newborn was deceased as of the newborn end date.

“AERR” indicates that the newborn record was added in error.


HISCA Alias



Data Element Name Masked Flag





Standard Reference

Definition The flag is used to mark whether the participant can be viewed on the web application. If the Masked Flag is '1' the user will see an error message in the web application, "The information being accessed is masked. This information may be available in Alberta Netcare Portal."


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline The value will be "1" if the individual is masked from view in the application. Otherwise the value will be "0".

Implementation Consideration If the participant has any open alerts, they will still be displayed in the Current Alerts page but the participant’s demographics would be masked from viewing. It is unlikely that this situation would occur as the newborn will not be masked until completion of the screening cycle.

For merged ULIs, if the masked flag is set on either the primary ULI or any of the secondary ULIs, the participant will not be displayed on the Screening History page. This will apply regardless if the primary ULI is a newborn or non-newborn. If the ULIs are later un-merged, the ULIs will retain their original masked flags.

Permissible Data Element Value 1 = masked

0 = not masked

HISCA Alias



Compound Name Parent Contact Information

Parent Compound Name Newborn

Component Name Parent ULI

Parent Surname

Parent First Given Name

Parent ULI Not Available Reason Code



Obligation

Cardinality


Standard Reference

Definition The demographic information for the parent, usually the mother, associated to the newborn at the time the newborn is registered or as updated within 90 days.




Data Element Name Parent ULI



Requirement for the Standard The ULI identifies the Newborns' parent to the newborn metabolic screening application



Definition The ULI (Unique Lifetime Identifier) is a unique and permanent number assigned to all persons of interest to the health system of Alberta. This includes Alberta residents and residents of other provinces who receive health services in Alberta.

Stakeholder-PERSON - a human being, alive or not, of interest to the health system.


Num



999999999

Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Parent ULI is received only for newborn ULIs.

Implementation Consideration Check digit routine available but not utilized by NMS.

Person Directory will only assign ULIs that pass the check-digit algorithm.


HISCA Alias Unique Lifetime Identifier



Data Element Name Parent Surname






Definition The parent’s last name. This field specifies the newborn parent's surname.


Char



Obligation O

Cardinality 0:1

Business Rule / Coding Guideline Parent Surname is received only for newborn ULIs.



HISCA Alias Last Name



Data Element Name Parent First Given Name






Definition The parent’s first name. This field specifies the newborn parent’s first name.


Char



Obligation O

Cardinality 0:1

Business Rule / Coding Guideline Parent First Given Name is received only for newborn ULIs.



HISCA Alias Given Name



Data Element Name Parent ULI Not Available Reason Code





Standard Reference

Definition A unique code identifying the reason no parent ULI was entered.


Char



Obligation O

Cardinality 0:1


Implementation Consideration The parent's ULI is used to link the newborn and parent in Person Directory/Central Stakeholder Registry.

This ULI may not be available in case of adoption or abandonment.


HISCA Alias



Compound Name Telephone


Component Name Home Phone Area Code

Home Phone Number

Phone Silent Indicator



Obligation

Cardinality


Standard Reference

Definition The telephone number associated to the newborn at the time the newborn is registered or as updated within 90 days.




Data Element Name Home Phone Area Code



Requirement for the Standard Used for clarification of a request or other information regarding the order. Also used for follow-up on screening alerts



Definition This specifies the area code of Newborn's phone number.

A code that further subdivides an international telecommunication zone into unique areas within zone, used to expedite the routing of telecommunication message to the desired place within the zone.


Char



Obligation O

Cardinality 0:1

Business Rule / Coding Guideline Home Phone Area Code is received only for newborn ULIs.

Implementation Consideration Home Phone Area Code: the database currently supports 4 chars and is compliant with the standard.


HISCA Alias Area Code



Data Element Name Home Phone Number



Requirement for the Standard Used for clarification of a request or other information regarding the order. Also used for follow-up on screening alerts



Definition This specifies the Newborn's phone number (excluding area code).

The number assigned to a telephone subscriber (unique within an area), to make connections to their telephone


Char



Obligation O

Cardinality 0:1

Business Rule / Coding Guideline Home Phone Number is received only for newborn ULIs.



HISCA Alias Local Phone Number



Data Element Name Phone Silent Indicator





Standard Reference

Definition Newborn phone silent indicator. If the Silent indicator is ‘Y’, it indicates that the phone number is not to be released or used for purposes other than standard business procedures.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline Phone silent indicator is received only for newborn ULIs.


Permissible Data Element Value 1 - yes

0 - no

HISCA Alias



Compound Name Birth Delivery Site


Component Name Facility Identifier

Facility Name



Obligation

Cardinality


Standard Reference

Definition The geographic or physical point of the specific site where the newborn was born or registered..




Data Element Name Facility Identifier





Standard Reference

Definition An identifier used to uniquely identify the hospital where the newborn was born or registered.


Num



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Birth delivery site data is received for newborn ULIs only.

Implementation Consideration Facility Identifier value is received from Person Directory (Central Stakeholder Registry extract).


HISCA Alias



Data Element Name Facility Name





Standard Reference

Definition Name of facility where the newborn was born or registered.


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Birth delivery site data is received for newborn ULIs only.

Implementation Consideration The facility name that arrives from Person Directory (Central Stakeholder Registry extract) does not get stored in the NMS database. Rather the Facility Identifier is used to map to a NMS Facilities table that identifies the facility name and subsequently assigns the record to a Zone (District) as of March 2010.


HISCA Alias



Compound Name Address


Component Name Address Line 1

Address Line 2

Address Line 3

City Name

Province State Code

Country Code

Postal Code

Bad Address Indicator

Temporary Address Indicator



Obligation

Cardinality


Standard Reference Stakeholder Demographic Standard

Definition Mailing address is the location at which a person (or organization) receives mail.




Data Element Name Address Line 1






Definition Address information is a collection of information pertaining to the address of the newborn. This specifies address line 1.

Description of location within a community or municipality, which specifies the destination for mail delivery, and/or the location of a stakeholder.


Char



Obligation O

Cardinality 0:1

Business Rule / Coding Guideline Address Line 1 is received only for newborn ULIs.



HISCA Alias Street Address









Definition An address is a place where a person or organization can be located or communicated with via postal services. Street, lock box, rural route and/or general delivery type information, general description of physical location. This specifies address line 2.



Char



Obligation O

Cardinality 0:1













Definition An address is a place where a person or organization can be located or communicated with via postal services. Street, lock box, rural route and/or general delivery type information, general description of physical location. This specifies address line 3.



Char



Obligation O

Cardinality 0:1







Data Element Name City Name






Definition Specifies the city of the newborn’s address.

A geographical location which has a name and operates as a community of stakeholders. These may or may not be legally incorporated locations, and may or may not be Canada Post delivery destinations.


Char



Obligation O

Cardinality 0:1

Business Rule / Coding Guideline City Name is received only for newborn ULIs.



HISCA Alias City Name



Data Element Name Province State Code






Definition Specifies the province of the newborn’s address.

Standard abbreviation for Canadian province or non-Canadian province or states.


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Province State Code is received only for newborn ULIs.

If there is no address specified, there may not be a province provided. A province code will only be required if there is an address and if the country is Canada or the USA.



HISCA Alias Province / State Code



Data Element Name Country Code





Standard Reference Stakeholder Demographic Data

Definition Specifies the country of the newborn’s address.

A code indicating a country or a country's subdivision.


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Country Code is received only for newborn ULIs.

Country Code is entered only if there is an address. A country code of USA or Canada will require a Province State Code.

Implementation Consideration The database currently supports 4 chars, 1 more than the standard. The length of the field in the CSR extract is 4 chars (blanks sent from CSR are stripped before storing in the database - e.g. "CAN " is stored as "CAN").


HISCA Alias Country Code



Data Element Name Postal Code






Definition Specifies the postal code of the newborn’s address.


Char



ANANAN

Obligation O

Cardinality 0:1

Business Rule / Coding Guideline Postal Code is received only for newborn ULIs.



HISCA Alias Postal Code



Data Element Name Bad Address Indicator





Standard Reference

Definition If the Bad address flag is 'Y' it indicates that mail for the stakeholder has been returned from the address. The accuracy of the address is questionable.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline Bad Address Indicator is received only for newborn ULIs.

Implementation Consideration 0 = No = "Good" address

1 = Yes = "Bad" address

Database stores 0s and 1s and the application displays Yes and No.


0 - no

HISCA Alias



Data Element Name Temporary Address Indicator





Standard Reference

Definition Newborn's address recorded as Temporary address.

The flag is used to mark communication information for an individual or organization as temporary


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline Temporary Address Indicator is received only for newborn ULIs.

Implementation Consideration 0 = No = Address is not temporary

1 = Yes = Address is temporary

Database stores 0s and 1s and the application displays Yes and No.


0 - no

HISCA Alias



Compound Name Newborn Transfer


Component Name Initiate Zone District

Destination Zone District

Transfer Start Date

Transfer Resolved Date

Transfer Status

Initiate Zone District Comment

Destination Zone District Comment



Obligation

Cardinality


Standard Reference

Definition Information regarding the transfer of responsibility of the newborn from one zone (district) to another.




Data Element Name Initiate Zone District





Standard Reference

Definition The identifier of the zone (district) initiating the transfer.


Num



Obligation M

Cardinality 1:1


Implementation Consideration This value is auto-populated by the zone (district) of responsibility that the newborn is currently assigned to.


HISCA Alias



Data Element Name Destination Zone District





Standard Reference

Definition The identifier of the zone (district) receiving the transfer request.


Num



Obligation M

Cardinality 1:1


Implementation Consideration This value is specified by the user who is initiating the transfer.


HISCA Alias



Data Element Name Transfer Start Date





Standard Reference

Definition The date that the transfer was initiated.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1


Implementation Consideration This date is auto-populated by the application when the transfer is initiated.


HISCA Alias



Data Element Name Transfer Resolved Date





Standard Reference

Definition The date that the transfer was resolved (i.e. canceled / accepted / declined).


Date / Time



YYYYMMDDHHMMSS

Obligation C

Cardinality 0:1

Business Rule / Coding Guideline As of the March 2009 release, all transfers are automatically accepted when they are created. The accepted date and closing comments will not be set as they would be the same as the initial date and comments.

Implementation Consideration This date is auto-populated by the application when the transfer is created.


HISCA Alias



Data Element Name Transfer Status





Standard Reference

Definition The status of the transfer action or event or request (i.e. pending / resolved).


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline As of the March 2009 release, all transfers are automatically accepted when they are created.


Permissible Data Element Value 0 = Pending

1 = Accepted

2 = Declined

3 = Cancelled

HISCA Alias



Data Element Name Initiate Zone District Comment





Standard Reference

Definition The comments indicate why the initiating zone (district) is performing a transfer.


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Comments may be entered by the user when the transfer is initiated.



HISCA Alias



Data Element Name Destination Zone District Comment





Standard Reference

Definition The comments indicate why the destination zone (district) is performing a specific action (i.e. decline / accept).


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Comments may be entered by the user when the transfer is resolved.

As of the March 2009 release, all transfers are automatically accepted when they are created. The accepted date and closing comments will not be set as they would be the same as the initial date and comments.



HISCA Alias



Compound Name Newborn Alert


Component Name Newborn Alert Date

Alert Code

Newborn Escalation Date

Newborn Alert End Reason



Obligation

Cardinality


Standard Reference

Definition Information related to a Missing Screen Event (MSE) or Missing Birth Event (MBE) alert.




Data Element Name Newborn Alert Date





Standard Reference

Definition The date that the alert, related to the registration, was created.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1

Business Rule / Coding Guideline This is set with the date when the alert is created.



HISCA Alias



Data Element Name Alert Code





Standard Reference

Definition Alerts generated related to a newborn registration, not related to a lab test result.


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline This code is set by the application when a Missing Screening Event (MSE) or Missing Birth Event (MBE) alert is created.


Permissible Data Element Value Missing Screening Event (MSE), Missing Birth Event (MBE)

See Alert-Interpretation Codes

HISCA Alias



Data Element Name Newborn Escalation Date





Standard Reference

Definition The date that the alert was escalated.


Date / Time



YYYYMMDDHHMMSS

Obligation C

Cardinality 0:1

Business Rule / Coding Guideline This date is set by the application when it deems that the alert should be escalated. Each alert has its own parameters of when it should be escalated.



HISCA Alias



Data Element Name Newborn Alert End Reason





Standard Reference

Definition This code indicates why the alert was ended.


Num



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline The end reason will be set when the application or user resolves the alert. Until the alert is resolved, the reason will be empty.

Implementation Consideration There is some duplication of textual descriptions of codes, which is expected as codes may come from various sources. The corresponding code number should be unique and should identify the source.

There is also, however, some duplication of descriptions and codes that cannot be explained, where some codes are not applicable to certain data elements. This will need to be investigated further by the vendor.


HISCA Alias



Compound Name Lab Order


Component Name Zone of Collection

Accession Number

Message Date Time

Lab Newborn Gender

Lab Newborn Birth Date

Lab Newborn Birth Time

Comments

Order Control Reason

Record End Reason Code

Birth Weight

Gestational Age

Lab Test Result

Specimen Collection Information

Lab Order Alert


Requirement for the Standard Lab orders and lab test results are required for reconciliation to birth events.

Obligation

Cardinality


Standard Reference

Definition An order is a request for material or services, usually for a specific patient. A lab order includes clinical observations (e.g., vitals, I & Os) from the nursing service, tests in the laboratory, films from radiology, etc.




Data Element Name Zone of Collection





Standard Reference

Definition The Zone collecting and submitting the newborn metabolic screening sample.


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline If a Zone of Collection is not submitted or is not valid, a default value of 0 (Unassigned) will be used.



HISCA Alias



Data Element Name Accession Number





Standard Reference

Definition This indicates the order number assigned to the NMS screening order by the lab


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline This is a unique number as of October 31, 2008.



HISCA Alias



Data Element Name Message Date Time





Standard Reference

Definition Date the message was generated.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1

Business Rule / Coding Guideline If the value is not valid or empty, the NMS batch will replace it with '18000101000000'. An email will be sent to the lab summarizing the substitution.



HISCA Alias



Data Element Name Lab Newborn Gender





Standard Reference

Definition For purposes of identification, the gender, as declared by the individual is captured. Gender refers to social or cultural categories, while the sex of an individual references biological categories.


Char



Obligation M

Cardinality 1:1




HISCA Alias Administrative Gender



Data Element Name Lab Newborn Birth Date



Requirement for the Standard Birth date is required to establish identity and age at collection.


Standard Reference

Definition Date of the birth recorded.


Date



YYYYMMDD

Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Lab Newborn Birth Time



Requirement for the Standard Birth time is required to establish identity and age at collection.


Standard Reference

Definition Time of the birth recorded in 24 hour clock.


Time



HHMM

Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Comments





Standard Reference

Definition Application generated comment that indicates why a Screen was ended (i.e. moved or cancelled)


Char



Obligation C

Cardinality 0:1


Implementation Consideration If the screen was ended by the application, then there will be a value in this field. If the lab ends the screen (value in Order Control Reason) these comments are also copied to the Comments field.


HISCA Alias



Data Element Name Order Control Reason





Standard Reference

Definition The reason given by the Lab, why the screen was cancelled.


Char



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline If the screen was cancelled by the lab, then there will be a value in this field.


At this time, the Lab and NMS application are not compliant with HL7 Messaging Standard v2.3, which provides 200 characters as a normative limit for ORC-16.


HISCA Alias



Data Element Name Record End Reason Code





Standard Reference

Definition This code specifies the reason why the screen was ended.


Num



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline The value is used by the batch to determine when an order has been cancelled. If a notification message is received this field is populated based on the notification tracking alert code.

Implementation Consideration If the screen was ended (value exists in either Comments or Order Control Reason), there would be a value in this field.


HISCA Alias



Data Element Name Birth Weight





Standard Reference LOINC code: 8339-4

Definition Body weight at birth, measured in grams


Num



Obligation M

Cardinality 1:1


Implementation Consideration LOINC codes are not sent in the HL7 message


HISCA Alias



Data Element Name Gestational Age





Standard Reference LOINC code: 76516-4

Definition Gestational age at birth, measured in weeks


Num



Obligation M

Cardinality 1:1


Implementation Consideration LOINC codes are not sent in the HL7 message


HISCA Alias



Compound Name Lab Test Result

Parent Compound Name Lab Order

Component Name Test Result Value

Test Result Test

Lab Test Alert


Requirement for the Standard Lab orders and lab test results are required for reconciliation to birth events.

Obligation

Cardinality


Standard Reference

Definition Results (final and updates) associated with a laboratory test.




Data Element Name Test Result Value

Compound Name Lab Test Result




Standard Reference

Definition Value associated with the result of the test.


Char



Obligation M

Cardinality 1:7




HISCA Alias



Compound Name Test Result Test

Parent Compound Name Lab Test Result

Component Name Test Type code

Test Description



Obligation

Cardinality


Standard Reference

Definition The lab test that was performed.




Data Element Name Test Type code





Standard Reference

Definition The Type of Test that was completed by the lab.


Char



Obligation M

Cardinality 1:1


Implementation Consideration Identifier for the Test Description - mapped within the application. Eg: Amino Acids = A


HISCA Alias



Data Element Name Test Description



Requirement for the Standard Required to identify the newborn metabolic test performed


Standard Reference

Definition A descriptive name for the test code. Example: "Amino Acids"


Char



Obligation M

Cardinality 1:1




HISCA Alias



Compound Name Specimen Collection Information


Component Name Collector Identifier

Collection Date Time

Specimen Received Date Time

Specimen Collection Site



Obligation

Cardinality


Standard Reference

Definition Specimen collection information describes detail related to specimen collection and receipt of specimen in the NMS Laboratory.




Data Element Name Collector Identifier





Standard Reference

Definition Alphanumeric identifier that may be assigned to a stakeholder (specimen collector) in the role of a service provider.


Char



Obligation O

Cardinality 0:1


Implementation Consideration This field contains the organization defined provider-number of the health service provider


HISCA Alias



Data Element Name Collection Date Time





Standard Reference

Definition Date the specimen was collected.


Date / Time



YYYYMMDDHHMM

Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Specimen Received Date Time





Standard Reference

Definition Date the screening sample was received by the NMS lab


Date / Time



YYYYMMDDHHMM

Obligation M

Cardinality 1:1




HISCA Alias



Compound Name Specimen Collection Site

Parent Compound Name Specimen Collection Information

Component Name


Requirement for the Standard Collection location is required for the purposes of quality assurance.

Obligation

Cardinality


Standard Reference

Definition The geographic or physical point of the location where the specimen was collected.




Data Element Name Collection Location Identifier

Compound Name Specimen Collection Site


Requirement for the Standard Collection location is required for the purposes of quality assurance.


Standard Reference

Definition An identifier used to identify the location where the specimen was collected as sent by the source system.


Char



Obligation O

Cardinality 0:1


Implementation Consideration Values are sent by the source system and the NMS application displays the value sent (no mapping is performed).


HISCA Alias



Compound Name Lab Test Alert

Parent Compound Name Lab Test Result

Component Name Lab Test Alert Date

Alert Code

Lab Test Escalation Date

Lab Test Alert End Reason



Obligation

Cardinality


Standard Reference

Definition Information related to alerts created from the laboratory reported test results.

Business Rule/Coding Guideline A birth event can have 0 or 1 Missing Screen Event alerts.

- A birth event can have 0 or 1 Missing Birth Event alerts.

- A Screen can have 0 or 1 Sample Quality alerts.

- A Screen can have 0 or more Invalid Data alerts, but can only have one for each alert code.

- A test can have 0 or 1 Major alerts.

- A test can have 0 or 1 Minor alerts.



Data Element Name Lab Test Alert Date





Standard Reference

Definition The date the alert was created by NMS.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1




HISCA Alias








Standard Reference

Definition Code specified in the laboratory reported test result which details type of follow up required, if any.


Char



Obligation M

Cardinality 1:1



Permissible Data Element Value Tracking code prefixed with "N"


HISCA Alias



Data Element Name Lab Test Escalation Date





Standard Reference

Definition The date the alert was escalated.


Date / Time



YYYYMMDDHHMMSS

Obligation C

Cardinality 0:1

Business Rule / Coding Guideline This date is set by the application when it deems that the alert should be escalated. Each alert has its own parameters of when it should be escalated.



HISCA Alias



Data Element Name Lab Test Alert End Reason





Standard Reference

Definition This field indicates why the alert was ended.


Num



Obligation C

Cardinality 0:1





HISCA Alias



Compound Name Lab Order Alert


Component Name Lab Order Alert Date

Alert Code

Lab Order Alert End Reason

Alert Action Information



Obligation

Cardinality


Standard Reference

Definition Information related to alerts created when there is discrepant or missing data.




Data Element Name Lab Order Alert Date





Standard Reference

Definition The date that the alert, related to the lab order, was created.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1

Business Rule / Coding Guideline This is set with the date when the alert is created.



HISCA Alias








Standard Reference

Definition Alerts generated when Lab processes a lab order, not related to a test result.


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline NOTE: Valid alert codes for a Lab Order Alert start with 'IDA'.


Permissible Data Element Value Invalid Data Alert (IDA) 1-9, Pending Overdue (PND)


HISCA Alias



Data Element Name Lab Order Alert End Reason





Standard Reference

Definition This field indicates why the alert was ended.


Num



Obligation C

Cardinality 0:1




HISCA Alias



Compound Name Alert Action Information

Parent Compound Name Lab Order Alert

Component Name Action Alert Date

Action Taken

Action Comment

Action Reason

Referral



Obligation

Cardinality


Standard Reference

Definition Information related to actions taken on newborn alerts, lab test alerts and lab order alerts.




Data Element Name Action Alert Date





Standard Reference

Definition The date the alert action occurred.


Date / Time



YYYYMMDDHHMMSS

Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Action Taken





Standard Reference

Definition Code used to represent the alert action.


Num



Obligation M

Cardinality 1:1


Implementation Consideration Used for alert follow-ups.


HISCA Alias



Data Element Name Action Comment





Standard Reference

Definition This field provides additional information as to why an action on the alert is being taken.


Char



Obligation O

Cardinality 0:1




HISCA Alias



Data Element Name Action Reason





Standard Reference

Definition This code provides additional information about an action taken on the alert or investigation related to the alert.


Num



Obligation C

Cardinality 0:1

Business Rule / Coding Guideline Current end reason of the alert at the time the action is taken upon the alert. If the alert is not closed, this value will be empty.

As of September 2009, this code will also be additional information about the investigation related to a missing birth event (MBE) alert.

As of September 2013, this code will also be additional information about steps taken in the investigation of missing screen event (MSE), minor, collection, and invalid data alerts.




HISCA Alias



Compound Name Referral

Parent Compound Name Alert Action Information

Component Name Full Name From

Full Name To

Phone Number

FAX Flag

Referral Date



Obligation

Cardinality


Standard Reference

Definition Contact information recorded about a referral of a newborn for follow up by a designated health service provider.

Business Rule/Coding Guideline Manually created referral for the newborn is based on Manually Close Alert with option "Follow-up initiated by NMS Lab” Or “Out of Province”



Data Element Name Full Name From





Standard Reference

Definition The person who initiated the referral.


Char



Obligation M

Cardinality 1:1


Implementation Consideration This data is specific to user access level or end-reason used.


HISCA Alias



Data Element Name Full Name To





Standard Reference

Definition The person or organization the referral was directed to


Char



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Phone Number





Standard Reference

Definition Phone or Fax number the referral was directed to.


Char



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Extension






Definition Phone extension number. A code that is assigned to individual telephone units collectively sharing the same router.


Char



Obligation O

Cardinality 0:1




HISCA Alias



Data Element Name FAX Flag





Standard Reference

Definition Indicates if referral was made by fax or phone.


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline Y = The contact number is a fax

N = The contact number is a phone (default)


Permissible Data Element Value "Y" = Fax

"N" = Phone

HISCA Alias



Data Element Name Referral Date





Standard Reference

Definition Date referral was initiated.


Date / Time



YYYYMMDDHHMM

Obligation M

Cardinality 1:1




HISCA Alias



Compound Name Alert Code

Parent Compound Name Newborn Metabolic Screening

Component Name Alert Code

Subclass Indicator

Short Description

Long Description

Escalate Flag

Escalate Number of Days

Birth Date Escalation Flag

First Alert Number of Days



Obligation

Cardinality


Standard Reference

Definition Alert codes (also known as interpretation codes) may be associated to a test result by the lab and transmitted to the NMS application. These test results and codes are then interpreted by NMS and alerts are generated in the application.

Alert (interpretation) codes are available in the Appendix of the HISCA submission document.









Standard Reference

Definition Codes sent by the lab or generated by the batch application which create alerts within the application.


Char



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Subclass Indicator





Standard Reference

Definition Indicates the type or severity of the alert.


Char



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Short Description





Standard Reference

Definition Short description of the alert for the purposes of display in the application.


Char



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Long Description





Standard Reference

Definition Full description of the alert.


Char



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Escalate Flag





Standard Reference

Definition Flag indicates whether the alert will be escalated or not escalated.


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline If "Y", the alert will be escalated if the conditions are met. If "N", the alert never escalates.


Permissible Data Element Value Y = the alert can be escalated.

N = the alert will not be escalated.

HISCA Alias



Data Element Name Escalate Number of Days





Standard Reference

Definition Threshold, number of days after which an alert will be escalated.


Num



Obligation M

Cardinality 1:1




HISCA Alias



Data Element Name Birth Date Escalation Flag





Standard Reference

Definition Indicates that the escalation is based on the birth date (rather than the alert date).


Char



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline If “Y”, then the time period to when the alert is escalated will be calculated from the newborn’s birth date. If the flag is set to “N”, then the alert will be escalated based on the alert date. There are only 2 alerts which are escalated based on the birth date: N39 (Increased tyrosine) and MSE.


Permissible Data Element Value Y = escalates from the newborn's birth date.

N = escalates from the alert creation date.

HISCA Alias



Data Element Name First Alert Number of Days





Standard Reference

Definition The number of days after which the alert will be created (Alert create Date).


Num



Obligation M

Cardinality 1:1

Business Rule / Coding Guideline Used for Missing Screen Event and Overdue Pending alerts.



HISCA Alias



VI. Permissible Values Newborn Gender Code Description Long Description

F Female

M Male

O Other

U Unknown

Birth Zone Code Description Long Description

31 South Zone

32 Calgary Zone

33 Central Zone

34 Edmonton Zone

35 North Zone

41 South Zone (East)

42 South Zone (West)

43 Central Zone (East)

44 Central Zone (West)

45 North Zone (Central)

46 North Zone (East)

47 North Zone (West)

0 Unassigned



Responsible Zone Code Description Long Description

31 South Zone

32 Calgary Zone

33 Central Zone

34 Edmonton Zone

35 North Zone

36 First Nations and Inuit Health Branch








0 Unassigned

Residence Zone Code Description Long Description

31 South Zone

32 Calgary Zone

33 Central Zone

34 Edmonton Zone

35 North Zone

0 Unassigned



Birth Order Code Description Long Description

1 Singleton or first of a multiple birth

2 Second of a multiple birth

3 Third of a multiple birth

4 Fourth of a multiple birth

5 Fifth of a multiple birth

6 Sixth of a multiple birth

7 Seventh of a multiple birth

8 Eighth of a multiple birth

9 Ninth of a multiple birth

Newborn End Reason Code Code Description Long Description

AERR Added in Error

DECD Deceased

Parent ULI Not Available Reason Code Code Description Long Description

NULI Unable to locate parent ULI / Adopted / Abandon

FEDS Parent RCMP or Armed Forces Member

OPPA Out of Province Mother/Father



Province State Code Code Description Long Description

AB Alberta

BC British Columbia

MB Manitoba

NB New Brunswick

NF Newfoundland

NS Nova Scotia

NT Northwest Territories &

NU Nunavut

ON Ontario

PE Prince Edward Island

QC Quebec

PQ Quebec

SK Saskatchewan

YT Yukon

AK Alaska

AL Alabama

AR Arkansas

AZ Arizona

CA California

CO Colorado

CT Connecticut

DC District of Columbia

DE Delaware

FL Florida

GA Georgia

HI Hawaii

IA Iowa

ID Idaho



Code Description Long Description

IL Illinois

IN Indiana

KS Kansas

KY Kentucky

LA Louisiana

MA Massachusetts

MD Maryland

ME Maine

MI Michigan

MN Minnesota

MO Missouri

MS Mississippi

MT Montana

NC North Carolina

ND North Dakota

NE Nebraska

NH New Hampshire

NJ New Jersey

NM New Mexico

NV Nevada

NY New York

OH Ohio

OK Oklahoma

OR Oregon

PA Pennsylvania

RI Rhode Island

SC South Carolina

SD South Dakota

TN Tennessee




TX Texas

UT Utah

VA Virginia

VT Vermont

WA Washington

WI Wisconsin

WV West Virginia

WY Wyoming

Initiate Zone District Code Description Long Description

31 South Zone

32 Calgary Zone

33 Central Zone

34 Edmonton Zone

35 North Zone










Destination Zone District Code Description Long Description

32 Calgary Zone

34 Edmonton Zone










Newborn Alert End Reason Code Description Long Description

1 Alert Resolved

4 Screen moved to another Birth Event

5 Screen Cancelled

7 Neonatal Death (CSR)

8 Birth Event added in Error

14 Neonatal Death

17 Out of province

18 Parental Refusal

19 Physician Refused

22 Resolved Under Another ULI

23 Stillborn

24 Unable to locate the family

28 Neonatal Death (LIS)

29 Screen Refused (Physician)

30 Screen Refused (Parent)

31 Birth Event Merged

32 Non-newborn ULI, no alternate ULI found

33 HDP# used - ULI not available

41 Parental non-compliance



Zone of Collection Code Description Long Description

31 South Zone

32 Calgary Zone

33 Central Zone

34 Edmonton Zone

35 North Zone

0 Unassigned

Lab Newborn Gender Code Description Long Description

F Female

M Male

U Unknown

Record End Reason Code Code Description Long Description

1 Cancelled

4 Newborn death in LIS

5 Physician refused from LIS

6 Parent refused from LIS



Test Type Code Code Description Long Description

A Amino acids

B Biotinidase

C IRT (Cystic Fibrosis)

D Data Quality

F Fatty acids

H 17-OH-Progesterone (CAH)

O Organic acids

Q Sample Quality

S TSH (CH)

T T4, Blood

X None

N Notification



Lab Test Alert End Reason Code Description Long Description

2 Test result changed

3 Repeat screen received

4 Screen moved to another birth event

5 Screen cancelled

7 Neonatal death (CSR/PD)

13 Follow-up initiated by NMS Lab

14 Neonatal death

15 No further follow-up required

17 Out of province

18 Parent/guardian refusal

19 Physician refusal


25 Has gone to private lab

41 Does not present

Lab Order Alert End Reason Code Description Long Description

1 Alert resolved


5 Screen cancelled

10 Closed manually



Action Taken Code Description Long Description

0 Repeat Ordered

1 Manual Close

2 Repeat Cancelled

3 Alert Reopened (Manual)

4 Application Close

5 Application Rescinded

6 Alert created

7 Alert Escalated

8 Comment Added

9 Alert Reopened (Application)

10 Alert De-escalated



Action Reason Code Description Long Description

1 Alert Resolved

2 Test result Changed

3 Repeat screen received


5 Screen cancelled

7 Neonatal death (PD)

8 Birth event added in error

10 Closed manually

13 Follow-up initiated by NMS Lab

14 Neonatal Death

15 No further follow-up required

17 Out of province

18 Parent/guardian refusal Closes alert - User

19 Physician refusal Closes alerts on the current alert page - User

22 Resolved under another ULI

23 Stillborn


25 Has gone to private lab

27 Closed by AMS

28 Neonatal death (LIS)

29 Physician refusal Close alert - LIS

30 Parent/guardian refusal Close alert - LIS

31 Birth event merged

32 Non-newborn ULI, no alternate ULI found

33 HDP# used - ULI not available

34 Collected under mom's ULI

35 NMS Lab entry error

36 Transcription error on requisition




37 Potential duplicate ULI found - PD merge requested

38 HDP# - ULI not provided

39 HDP# - ULI illegible / invalid

40 HDP# - demographics require confirmation

41 Does not present

42 Distributed: Sent to AHS Zone

43 Distributed: Sent to FNIHB

44 Distributed: Re-sent to AHS Zone

45 Distributed: Re-sent to FNIHB

46 Data Verification: Pending

47 Data Verification: Correction Requested

48 Investigation and Monitoring: NMS Lab Consultation

49 Investigation and Monitoring: HIM Consultation

50 Investigation and Monitoring: Zone PHN Consultation

51 Investigation and Monitoring: FNIHB Consultation

52 Investigation and Monitoring: No further action until 90 days

53 Investigation and Monitoring: Administrative closure requested

54 Sample Collection: Pending

55 Sample Collection: Appointment Booked

56 Sample Collection: Completed

57 Sample Collection: Pending Referred to Midwife

58 Sample Collection: Pending Referred to NICU/SCN

59 Sample Collection: Pending Due to Transfer

60 Sample Collection: Not Required - Collected Under Alternate ULI or HDP#

61 Sample Collection: Not Required - Neonate Stillborn or Deceased



Subclass Indicator Code Description Long Description

A Major

B Missing Birth Event

C Minor

D Deceased

I Collection

P Overdue Pending

R Refusal

S Missing Screen Event

V Invalid data received



Alert Code - N codes (Alert-Interpretation Codes) Alert Code

Test Type Subclass Indicator / Alert Type

Display Description Comments

N25 Sample Quality Collection < 24 Hours N28 Amino acids Major Abnormal PKU screen N32 Biotinidase Major Confirmed abnormal BIOT

screen

N37 Biotinidase Minor Borderline abnormal BIOT screen

N39 Amino acids Minor Increased tyrosine N40 Amino acids Minor Borderline abnormal PKU

screen Updated the description for September 2010 (SR 10078)

N41 Notification Deceased Deceased N43 TSH (CH) Major Abnormal CH screen New December 2006 (SR 06536) N44 TSH (CH) Minor Borderline abnormal CH

screen New December 2006 (SR 06536)

N45 Biotinidase Minor Borderline abnormal BIOT screen

New March 2010 (SR 09608)

N49 Sample Quality Collection Requisition Expired New June 2010 N50 Sample Quality Collection Date or time of birth illegible

or not indicated New April 2007 (SR 06854)

N51 Sample Quality Collection Date/time of collection illegible or not indicated

New April 2007 (SR 06854)

N52 Sample Quality Collection Sample insufficient (NSQ) New April 2007 (SR 06854) N53 Sample Quality Collection Sample contaminated New April 2007 (SR 06854) N54 Sample Quality Collection Poor elution New April 2007 (SR 06854) N55 Sample Quality Collection Specimen fixed to filter

paper New April 2007 (SR 06854)

N56 Sample Quality Collection Blood clotted and layered New April 2007 (SR 06854) N57 Sample Quality Collection Specimen abraded New April 2007 (SR 06854) N58 Sample Quality Collection Query patient identification New April 2007 (SR 06854) N59 Notification Refusal Parent refusal New April 2007 (SR 06854) N60 Notification Refusal Physician refusal New April 2007 (SR 06854) N70 Amino acids Major Abnormal MSUD screen New April 2007 (SR 06854) N71 Amino acids Major Abnormal CIT screen New April 2007 (SR 06854) N72 Organic acids Major Abnormal GA1 screen New April 2007 (SR 06854) N73 Organic acids Major Abnormal HMG screen New April 2007 (SR 06854) N74 Organic acids Major Abnormal IVA screen New April 2007 (SR 06854) N75 Organic acids Major Abnormal MMA screen New April 2007 (SR 06854) N76 Organic acids Major Abnormal MMA/PA screen New April 2007 (SR 06854) N77 Fatty acids Major Abnormal MCAD screen New April 2007 (SR 06854) N78 Fatty acids Major Abnormal LCHAD/TFP

screen New April 2007 (SR 06854)

N79 Fatty acids Major Abnormal CUD screen New April 2007 (SR 06854) N80 Fatty acids Major Abnormal VLCAD screen New April 2007 (SR 06854) N81 17-OH-

Progesterone (CAH) Major Abnormal CAH screen New April 2007 (SR 06854)

N82 IRT (Cystic Fibrosis) Major Abnormal CF screen (2 mutations)


N83 IRT (Cystic Fibrosis) Major Inconclusive CF screen New April 2007 (SR 06854)



Alert Code

Test Type Subclass Indicator / Alert Type

Display Description Comments

N84 Amino acids Minor Borderline abnormal MSUD screen


N85 Amino acids Minor Increased amino acids New April 2007; replaces N38 - comments will indicate which amino acids are increased (SR 06854)

N86 Organic acids Minor Increased organic acylcarnitines

New April 2007; comments will indicate which acylcarnitines are increased (SR 06854)

N87 Organic acids Minor Borderline abnormal GA1 screen


N88 Organic acids Minor Borderline abnormal HMG screen


N89 Organic acids Minor Borderline abnormal IVA screen


N90 Organic acids Minor Borderline abnormal MMA screen


N91 Organic acids Minor Borderline abnormal MMA/PA screen


N92 Fatty acids Minor Borderline abnormal MCAD screen


N93 Fatty acids Minor Borderline abnormal LCHAD/TFP screen


N94 Fatty acids Minor Borderline abnormal CUD screen


N95 Fatty acids Minor Borderline abnormal VLCAD screen


N96 17-OH-Progesterone (CAH)

Minor Borderline abnormal CAH screen


N97 Fatty acids Minor Increased fatty acylcarnitines

New April 2007; comments will indicate which acylcarnitines are increased (SR 06854)

N98 Amino acids Major Marked Increased Tyrosine New April 2007 (SR 06854) N99 IRT (Cystic Fibrosis) Major Markedly increased IRT, no

mutations identified New July 2009 (client email request, no SR)

N100 None Collection Absence of Alert New September 2007 (SR 07489)



Alert Code – Non-N codes (Alert-Interpretation Codes) Alert Code

Test Type

Subclass Indicator / Alert Type

Display Description

Comments

IDA1 None Invalid Data

Collection Date is in the future.

New October 2008 (AM074)


Collection Date is before the PD Birth Date



Collection Date is an invalid date.



Birth Date on the Requisition is in the future



Requisition DoB is different from demographic DoB



Birth Date on the Requisition is an invalid date



Specimen Received Date is before Collection Date

New September 2009 (SR 09021)


Specimen Received Date is before the PD Birth Date



Lab Gender is different from Demographic Gender


MBE None Missing Birth Event

Missing Birth

MSE None Missing Screen Event

Missing Screening

PND None Overdue Pending

Overdue Pending New June 2010 (SR 09867)