IPD | IPD-001 | to be reviewed | Testable |
0
|
0
| | Constraints in eHDSI ePrescription SHALL apply to all Prescription documents. | 11 | Section 3 | 7/8/20 10:56:14 AM by sryan |
|
IPD | IPD-002 | to be reviewed | Testable |
0
|
0
| | Constraints in Patient Summary Interoperability specification, section 2 on conformance requirementsSHALL apply to all Prescription documents. | 11 | Section 3 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-003 | to be reviewed | Testable |
0
|
0
| | The language SHALL be present. | 11 | Section 3 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-004 | to be reviewed | Testable |
0
|
0
| | Constraints in Patient Summary content Interoperability specification, section on CDA Header attributes and constraints SHALL apply to all Prescription documents. | 11 | Section 4 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-005 | to be reviewed | Testable |
0
|
0
| | The Author SHALL contain one [1..1] assignedAuthorthat SHALL NOT be null flavor. | 11 | Section 4 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-006 | to be reviewed | Testable |
0
|
0
| | If assignedAuthor has an associated representedOrganization with no assignedPerson or assignedAuthoringDevice, then the value for ClinicalDocument/author/assignedAuthor/id/@NullFlavor SHALL be "NA""Not applicable" 2.16.840.1.113883.5.1008 NullFlavor. | 11 | Section 4 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-007 | to be reviewed | Testable |
0
|
0
| | The Patient gender SHALL be present | 11 | Section 4 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-008 | to be reviewed | Testable |
0
|
0
| | Constraints in eHDSI ePrescription substance Administration entry SHALL apply to all Prescription documents. | 14 | Section 5 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-009 | to be reviewed | Testable |
0
|
0
| | Prescription section SHALL contain one [1..1] medication item | 15 | Section 5 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-010 | to be reviewed | Testable |
0
|
0
| | Constraints in eHDSI ePrescription Manufactured Product entry SHALL apply to all Prescription documents. | 17 | Section 5 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-011 | to be reviewed | Testable |
0
|
0
| | Constraints in the IHE IT Infrastructure (ITI) Volume 3 (ITI TF-3) Section 5.2 Scanned Document Content Profile XDS-SD using the PDF or plaintext Option [R10] SHALL apply to all clinical scanned ePrescription documents. | 17 | Section 6 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPD | IPD-012 | to be reviewed | Testable |
0
|
0
| | Constraints on CDA Header attributes described in [R8] SHALL apply to all clinical scanned ePrescription documents. | 17 | Section 6 | 12/18/20 3:42:27 PM by aeschlimann |
|
IPIM | IPIM-002 | to be reviewed | Testable |
1
|
0
| | PPSN: The PPSN SHALL be supported. It MAY be issued in a PDQ query request. When issued, it SHALL be conveyed with a <Assigning Authority ID> to identify the DSP as its assigning authority and an <ID number> to identify the IHI number. The <Assigning Authority ID> (placed in the HL7V2.5 universal ID) shall be set to 1.2.372.980010.1.1. | 17 | Section 5.1.1 | 6/24/20 3:29:05 PM by sryan |
|
IPIM | IPIM-003 | to be reviewed | Testable |
0
|
0
| | IHI: The heath identifier used for sharing of patient records. The <Assigning Authority ID> identifies the IHI assigning authority and the <ID number> identifies the IHI Number. The <Assigning Authority ID> (placed in the HL7 V2.5 universal ID) SHALL be set to 1.2.372.980010.1.2. | 17 | Section 5.1.1 | 12/18/20 3:42:27 PM by sryan |
|
IPIM | IPIM-004 | to be reviewed | Testable |
0
|
0
| | National European ID Card (EHIC number): This identifier is issued by national health insurance providers in Europe. The <Assigning Authority ID> identifies the national health insurance provider who is the issuing authority of the National ID Card and the <ID number> identifies the National ID specific to a patient. The <Assigning Authority ID> (placed in the HL7V2.5 universal ID)shall be set to 1.2.372.980010.1.3.<ISO 3166-1 Numeric Code for Country>. | 18 | Section 5.1.1 | 12/18/20 3:42:27 PM by sryan |
|
IPIM | IPIM-005 | to be reviewed | Testable |
0
|
0
| | Passport Number: These identifiers are generated by the various national passport issuing authorities for their citizen issued passports that come to Ireland as visitors. The < Assigning Authority ID> identifies the Nation who is the issuing authority of the passport number and the <ID number> identifies the issued Passport Number. The < Assigning Authority ID> (placed in the HL7V2.5 universal ID)SHALL be set to 1.2.372.980010.1.4.<ISO 3166-1 Numeric Code for Country>. | 18 | Section 5.1.1 | 12/18/20 3:42:27 PM by sryan |
|
IPIM | IPIM-006 | to be reviewed | Testable |
1
|
0
| | Patient Name: Specifies the name of the person whose information is being queried. The Patient Demographics Consumer Actor SHALL support the capture of this attribute, and if captured, sending it in the query transaction. Both Family Name (XPN-1) and Given Name (XPN-2) component elements SHALL be sent. The middle name, if available, SHALL be sent using the Second And Further Given Names Or Initials Thereof (XPN-3) component element. | 18 | Section 5.1.1 | 6/25/20 12:22:38 PM by sryan |
|
IPIM | IPIM-007 | to be reviewed | Testable |
1
|
0
| | Gender: specifies the administrative gender of the person whose information is being queried. The Patient Demographics Consumer Actor SHALL support the capture of this attribute, and if captured, sending it in the query transaction. | 19 | Section 5.1.1 | 6/25/20 12:22:42 PM by sryan |
|
IPIM | IPIM-008 | to be reviewed | Testable |
0
|
0
| | Gender: The supported code values SHALL be one of the codes defined in the Administrative Gender Value Set with an OID=2.16.840.1.113883.5.1 specified in the General Terminology Interoperability Specification. | 19 | Section 5.1.1 | 12/18/20 3:42:27 PM by sryan |
|
IPIM | IPIM-009 | to be reviewed | Testable |
1
|
0
| | Birth Date- Specifies the birth date of the person in the Gregorian calendar whose information is being queried. The Patient Demographics Consumer Actor SHALL support the capture of this attribute, and if captured, sending it in the query transaction. The contents SHALL NOT contain time but contain the greatest degree of detail among year, month, and day as is available. | 19 | Section 5.1.1 | 6/25/20 12:23:21 PM by sryan |
|