76
ICH ICSR Implementation Guide 12 April 2013
-77-
The root indicates the namespace of D.1.1.1, the actual medical record
number is populated at id extension. The code of ‘gpmn’ is populated to
distinguish from D.1.1.2 to D.1.1.4.
D.1.1.2 Patient Medical Record Number(s) and Source(s) of the Record Number
(Specialist Record Number)
User Guidance See Section D.1.1.
Conformance Optional
Data Type 20AN
OID 2.16.840.1.113883.3.989.2.1.1.4and 2.16.840.1.113883.3.989.2.1.3.8
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.2:
id extension="medical record
number"root="2.16.840.1.113883.3.989.2.1.3.8"/
code code="specialistMrn"codeSystem="2.16.840.1.113883.3.989.2.1.1.4"/
The root indicates the namespace of D.1.1.2, the actual medical record
number is populated at id extension. The code of ‘specialistMrn’ is
populated to distinguish from D.1.1.1, D.1.1.3 and D.1.1.4.
D.1.1.3 Patient Medical Record Number(s) and Source(s) of the Record Number (Hospital
Record 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.9
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.3:
id extension=" medical record number "
root="2.16.840.1.113883.3.989.2.1.3.9"/
code code="hospitalMrn"codeSystem="2.16.840.1.113883.3.989.2.1.1.4"/
The root indicates the namespace of D.1.1.3, the actual medical record
number is populated at id extension. The code of ‘hospitalMrn’ is
populated to distinguish from D.1.1.1, D.1.1.2 and D.1.1.4.
ICH ICSR Implementation Guide 12 April 2013
-77-
The root indicates the namespace of D.1.1.1, the actual medical record
number is populated at id extension. The code of ‘gpmn’ is populated to
distinguish from D.1.1.2 to D.1.1.4.
D.1.1.2 Patient Medical Record Number(s) and Source(s) of the Record Number
(Specialist Record Number)
User Guidance See Section D.1.1.
Conformance Optional
Data Type 20AN
OID 2.16.840.1.113883.3.989.2.1.1.4and 2.16.840.1.113883.3.989.2.1.3.8
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.2:
id extension="medical record
number"root="2.16.840.1.113883.3.989.2.1.3.8"/
code code="specialistMrn"codeSystem="2.16.840.1.113883.3.989.2.1.1.4"/
The root indicates the namespace of D.1.1.2, the actual medical record
number is populated at id extension. The code of ‘specialistMrn’ is
populated to distinguish from D.1.1.1, D.1.1.3 and D.1.1.4.
D.1.1.3 Patient Medical Record Number(s) and Source(s) of the Record Number (Hospital
Record 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.9
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.3:
id extension=" medical record number "
root="2.16.840.1.113883.3.989.2.1.3.9"/
code code="hospitalMrn"codeSystem="2.16.840.1.113883.3.989.2.1.1.4"/
The root indicates the namespace of D.1.1.3, the actual medical record
number is populated at id extension. The code of ‘hospitalMrn’ is
populated to distinguish from D.1.1.1, D.1.1.2 and D.1.1.4.