[WWW - 2023.07.31]
Identifying and Definitional Attributes
QH 042471 v1
Data Element
Data Element
Draft
10-Oct-2019
Standard
Information Management Strategic Governance Committee (IMSGC), Queensland Health
01-Jul-2016
The record category that prefixes an electronic Queensland Perinatal Data Collection (QPDC) data record.
Queensland Perinatal Data Collection (QPDC)
Record type (QPDC)
Representational Attributes
Alphabetic
Code
A
1
1
Permissible Values

Permissible_values

CodeDescription
BBaby's birth details
CMother's code
DBaby's birth code
FFile header
MMother's details
TType details
Supplementary Values

Supplemenary_values

-
Collection and Usage Attributes
The data is contained in a single file containing a number of different record types.

F File header
This contains information related to the file such as the file's extract period. There is one of these records in the file and it should be the first record in the file.

T Type details
This record contains counts of New, Amend and Delete record types that occur in the file. There will be one of these records for each of the record types Mother's details, Mother's code, Baby's birth details and Baby's birth code. A data type field on a Type details record identifies the record type that the counts relate to. The data types are:
Data type M Mother's details
Data type C Mother's code
Data type B Baby's birth details
Data type D Baby's birth code

These records should occur at the end of the file in the above order.

M Mother's details
This record contains the data related to the mother in a particular confinement. The data values that uniquely identify a particular confinement are the mother's UR number and the date of confinement. There is one mother detail record per confinement.

C Mother's code
Mother's code records are used to contain the multiple codes that relate to the mother in a confinement such as medical condition codes or conception method codes.

The mother's UR number and date of confinement fields on the record identify the confinement it is associated with and the Code type field identifies the particular code involved. The Code types are:
Code type C Conception method
Code type T Reason for transfer
Code type M Medical condition
Code type P Pregnancy complication
Code type O Procedure/operation
Code type L Method of delivery of last birth
Code type A Antenatal care type
Code type E Extra text

For each particular confinement and Code type, there can be multiple code values and thus multiple records. However, a particular code value can only occur once for a particular confinement and Code type. An example of this for a particular confinement is as follows:
Code type C, Code value 02
Code type C, Code value 19
Code type M, Code value B373
Code type M, Code value E669
Code type P, Code value O440
Code type P, Code value O16

Note that for example, another instance of Code type C, Code value 02 for the same confinement is not valid.

B Baby's birth details
These records contain the details relating to each birth of a baby for a confinement. A baby's birth is uniquely identified by the mother's UR number, the date of confinement and the baby number which is the birth order of the baby e.g. 1=twin 1, 2=twin 2, 1=singleton.

There is one of these records per birth per confinement and therefore there can be more than one Baby's birth detail record for each Mother's detail record.

D Baby's birth code
Baby's birth code records are used to contain the multiple codes that relate to a baby's birth in a confinement such as analgesia codes or congenital anomaly codes. The Mother's UR number, date of confinement and baby number fields on the record identify the baby's birth it is associated with and the Code type field identifies the particular code involved. The Code types are:
Code type I Induction/augmentation
Code type A Pharmacological analgesia
Code type S Anaesthesia
Code type R Resuscitation
Code type T Neonatal treatment
Code type C Congenital anomaly
Code type L Labour and delivery complication
Code type M Neonatal morbidity
Code type P Puerperium complication
Code type N Non-pharmacological analgesia
Code type F Type of fluid received in 24 hours prior to discharge
Code type D Type of fluid received at anytime during the birth episode
Code type E Extra text
Code type B Alternative feeding method code
Code type G Thromboprophylaxis code
Code type V Perineal status code

For each particular baby's birth and Code type, there can be multiple code values and thus multiple records.

However, a particular code value can only occur once for a particular baby's birth and Code type. This is similar to the Mother's code records.
Must be B, C, D, F, M or T.
The File header record is the first record in the file and there must be only one file header record.

Following the File header are the sets of records for each confinement. The confinement sets are ordered by increasing confinement date and within confinement date by increasing UR No. Each set of records for a confinement is made up in the following way:

- The Mother's detail record is the first record in a confinement set. There must be only one Mother's detail record per confinement set.

- Following the Mother's detail record are the Mother's code records if applicable. There can be zero to several records per code type and the records for each code type are grouped together. The ordering of the code types is C, T, M, P, O, L, A, E. Each group of records for a code type need not have any particular record order.

- Following the Mother's code records (if any) are Baby's birth record sets.

There must be at least one Baby's birth record set per confinement set, with the number of Baby's birth records matching the number of babies in the confinement. These sets are ordered by increasing Baby number. These sets are made up in the following way:

- The Baby's birth detail record is the first record in the set. There is only one Baby's birth detail record per Baby's birth set.

- Following the Baby's birth detail record are the Baby's birth code records if there are any. There can be zero to several records per code type and the records for each code type are grouped together. The ordering of these types is I, A, S, R, T, C, L, M, P, N, F, D, E, B, G, V. Each group of records for a code type need not have any particular record order.

The last four rows of the file will contain the Type detail records. These will show the counts of New, Amend and Delete records contained within the file. There is one of these records per each Data type and the ordering of the Data types is M, C, B, D.
Relational Attributes
Related Metadata References

Related Metadata References_IR

  • 1 - 15
ViewRelationshipMetadata Item TypeMetadata Item SubtypeNameIdentifier & VersionApproval Status
Is used in conjunction withData ElementData ElementBirth event-place of delivery, codeQH 042520 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-baby's code typeQH 042589 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-data extract dateQH 042621 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-data extract nominal monthly periodQH 041417 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-data extract period end dateQH 042620 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-data extract period start dateQH 042619 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-data typeQH 042538 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-extra text indicatorQH 042536 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-mother's code typeQH 042573 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-number of data extract records for amendmentQH 042724 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-number of data extract records for deletionQH 042768 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-number of new recordsQH 042723 Version 1Draft
Is used in conjunction withData ElementData ElementQueensland Perinatal Data Collection (QPDC)-record transaction typeQH 042771 Version 1Draft
Is used in conjunction withData ElementDerived Data ElementQueensland Perinatal Data Collection (QPDC)-baby's birth codeQH 042590 Version 1Draft
Is used in conjunction withData ElementDerived Data ElementQueensland Perinatal Data Collection (QPDC)-mother's codeQH 042062 Version 1Draft
Implementation in Metadata Sets

Implemented

  • 1 - 12
ViewMetadata Item TypeMetadata Item SubtypeNameIdentifer & VersionObligationApproval StatusEffective FromEffective To
Information AssetData CollectionQueensland Perinatal Data Collection (QPDC)QH 020003 Version 2MandatoryCurrent01-Jul-2019
Information AssetData CollectionQueensland Perinatal Data Collection (QPDC)QH 020003 Version 1MandatorySuperseded01-Jul-201630-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Baby Data Supply Requirement (DSR) 2016-2017QH 020355 Version 1MandatorySuperseded01-Jul-201630-Jun-2017
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Baby Data Supply Requirement (DSR) 2017-2018QH 020358 Version 1MandatorySuperseded01-Jul-201730-Jun-2018
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Baby Data Supply Requirement (DSR) 2018-2019QH 020449 Version 1MandatorySuperseded01-Jul-201830-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Baby Data Supply Requirement (DSR) 2019-2020QH 020570 Version 1MandatorySuperseded01-Jul-201930-Jun-2020
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Baby Data Supply Requirement (DSR) 2020-2021QH 020700 Version 1MandatorySuperseded01-Jul-202030-Jun-2021
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2016-2017QH 020321 Version 1MandatorySuperseded01-Jul-201630-Jun-2017
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2017-2018QH 020354 Version 1MandatorySuperseded01-Jul-201730-Jun-2018
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2018-2019QH 020448 Version 1MandatorySuperseded01-Jul-201830-Jun-2019
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2019-2020QH 020569 Version 1MandatorySuperseded01-Jul-201930-Jun-2020
Data Supply RequirementHHS Service AgreementQueensland Perinatal Data Collection (QPDC) Mother Data Supply Requirement (DSR) 2020-2021QH 020711 Version 1MandatorySuperseded01-Jul-202030-Jun-2021
Source and Reference Attributes