77
ICH ICSR Implementation Guide 12 April 2013
-78-
D.1.1.4 Patient Medical Record Number(s) and Source(s) of the Record Number
(Investigation Number)
User Guidance See Section D.1.1.
Conformance Optional
Data Type 20AN
OID 2.16.840.1.113883.3.989.2.1.1.4 and 2.16.840.1.113883.3.989.2.1.3.10
Value Allowed Free text
nullFlavor: MSK
Business Rule(s)
Please see Section 3.3.6 for further guidance on the use of nullFlavor to
describe missing or non-transmitted information.
The following notation will be used to represent D.1.1.4:
id extension=" medical record number "
root="2.16.840.1.113883.3.989.2.1.3.10"/
code code="investigation"codeSystem="2.16.840.1.113883.3.989.2.1.1.4"/
The root indicates the namespace of D.1.1.4, the actual medical record
number is populated at id extension. The code of ‘investigation’ is
populated to distinguish from D.1.1.1 to D.1.1.3.
D.2 Age Information
Only one of the elements describing age should be used. The choice should be based upon the
most precise information available and in conformance with the regional confidentiality
requirements.
D.2.1 Date of Birth
User Guidance This data element captures the full precision date (e.g. day, month, year)
for the date of birth of the patient. If the full date of birth is not known, an
approximate age can be captured in Section D.2.2.Alternatively, the
‘Patient Age Group (as per reporter)’ (D.2.3) can be used to indicate the
age of the patient.
Conformance Optional
Data Type Date /Time
OID None
Value Allowed See Appendix II for further information.
nullFlavor: MSK
Business Rule(s)
Minimum precision required is the day (i.e. ‘CCYYMMDD’).
The date specified cannot refer to a future date.
If the date of birth is known to the sender but cannot be transmitted due to
data privacy requirements, this data element should be left blank with
nullFlavor =MSK.
Please see Section 3.3.6 for further guidance on the use of nullFlavor to
describe missing or non-transmitted information.
ICH ICSR Implementation Guide 12 April 2013
-78-
D.1.1.4 Patient Medical Record Number(s) and Source(s) of the Record Number
(Investigation Number)
User Guidance See Section D.1.1.
Conformance Optional
Data Type 20AN
OID 2.16.840.1.113883.3.989.2.1.1.4 and 2.16.840.1.113883.3.989.2.1.3.10
Value Allowed Free text
nullFlavor: MSK
Business Rule(s)
Please see Section 3.3.6 for further guidance on the use of nullFlavor to
describe missing or non-transmitted information.
The following notation will be used to represent D.1.1.4:
id extension=" medical record number "
root="2.16.840.1.113883.3.989.2.1.3.10"/
code code="investigation"codeSystem="2.16.840.1.113883.3.989.2.1.1.4"/
The root indicates the namespace of D.1.1.4, the actual medical record
number is populated at id extension. The code of ‘investigation’ is
populated to distinguish from D.1.1.1 to D.1.1.3.
D.2 Age Information
Only one of the elements describing age should be used. The choice should be based upon the
most precise information available and in conformance with the regional confidentiality
requirements.
D.2.1 Date of Birth
User Guidance This data element captures the full precision date (e.g. day, month, year)
for the date of birth of the patient. If the full date of birth is not known, an
approximate age can be captured in Section D.2.2.Alternatively, the
‘Patient Age Group (as per reporter)’ (D.2.3) can be used to indicate the
age of the patient.
Conformance Optional
Data Type Date /Time
OID None
Value Allowed See Appendix II for further information.
nullFlavor: MSK
Business Rule(s)
Minimum precision required is the day (i.e. ‘CCYYMMDD’).
The date specified cannot refer to a future date.
If the date of birth is known to the sender but cannot be transmitted due to
data privacy requirements, this data element should be left blank with
nullFlavor =MSK.
Please see Section 3.3.6 for further guidance on the use of nullFlavor to
describe missing or non-transmitted information.