AssertionManagerGui

Id scheme	Assertion id	Status	Testable?	#Coverage	#Applies to	Predicate	Page	Tags	Last changed
1 2 3 4 5
ACP	ACP-001	to delete	Testable	1	0	The Attribute Value must be a child element PatientId in the urn:hl7-org:v3 namespace, with root and extension attributes.	12	Section 3.1	10/3/22 5:47:10 PM by rjohnson
ACP	ACP-002	to be reviewed	Testable	1	0	When specified, only one patient ID may be given in a single policy document, and it must appear as a descendent of <Target> element that is a direct child of the root <Policy> element.	12	Section 3.1	5/24/17 8:53:29 AM by aberge
ACP	ACP-003	to be reviewed	Testable	1	0	The Home Community ID must be an Object Identifier (OID), using the urn format (that is, urn:oid: appended with the OID).	12	Section 3.1	5/24/17 8:53:48 AM by aberge
ACP	ACP-004	to be reviewed	Testable	1	0	Document Class must be a Document Class code defined in the NHIN document metadata specifications. These are LOINC codes	12	Section 3.1	5/24/17 8:54:01 AM by aberge
ACP	ACP-005	to be reviewed	Testable	1	0	The User ID must be specified as either an e-mail address (rfc822Name) or an X500 name (x500Name)	12	Section 3.1	5/24/17 8:54:15 AM by aberge
ACP	ACP-006	to be reviewed	Testable	1	0	One of authorPerson or authorInstitution elements should be used to provide information about the author of the Access Consent Policy	13	Table 1	5/24/17 8:54:24 AM by aberge
ACP	ACP-007	to be reviewed	Testable	1	0	classCode must use the LOINC code 57017-6to represent Access Consent Policy. The description for this code is Privacy Policy.	13	Table 1	5/24/17 8:54:26 AM by aberge
ACP	ACP-008	to be reviewed	Testable	1	0	The value of the eventCodeList is an OID, which must be prefixed with urn:oid:. Since OIDs do not have a coding scheme, use the value N/A in the coding scheme slot	13	Table 1	5/24/17 8:54:32 AM by aberge
ACP	ACP-009	to be reviewed	Testable	1	0	Lack of serviceStartTime/serviceStopTime must be interpreted as meaning that the policy is not time limited	13	Table 1	5/24/17 8:54:39 AM by aberge
ACP	ACP-010	to be reviewed	Testable	1	0	typeCode must use the LOINC code 57017-6 to represent Access Consent Policy. The description for this code is Privacy Policy.	13	Table 1	5/24/17 8:54:52 AM by aberge
AUTH	AUTH-001	to be reviewed	Testable	0	0	All inter-node requests on the NHIN must utilize the Authorization Framework.	8	Section 2.2	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-002	to be reviewed	Testable	0	0	The initiating NHIO is required to and is responsible for the authentication and authorization of its users.	8	Section 2.2	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-003	to be reviewed	Testable	0	0	The initiating NHIO must include all REQUIRED attributes in each request.	8	Section 2.2	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-004	to be reviewed	Testable	0	0	SAML:Assertion is required within the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-005	to be reviewed	Testable	0	0	SAML:Assertion/@Version attribute is required in the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-006	to be reviewed	Testable	0	0	SAML:Assertion/@ID attribute is required in the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-007	to be reviewed	Testable	0	0	SAML:Assertion/@IssueInstant attribute is required in the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-008	to be reviewed	Testable	0	0	SAML:Assertion/Issuer element is required in the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-009	to be reviewed	Testable	0	0	SAML:Assertion/Subject element is required in the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge
AUTH	AUTH-010	to be reviewed	Testable	0	0	SAML:Assertion/AuthnStatement element is required in the <Security> element of the SOAP header.	10	Figure 1	9/13/17 1:29:56 PM by aberge

to delete

Testable

The Attribute Value must be a child element PatientId in the urn:hl7-org:v3 namespace, with root and extension attributes.

12

Section 3.1

10/3/22 5:47:10 PM by rjohnson

ACP

ACP-002

to be reviewed

Testable

1

0

When specified, only one patient ID may be given in a single policy document, and it must appear as a descendent of <Target> element that is a direct child of the root <Policy> element.

12

Section 3.1

5/24/17 8:53:29 AM by aberge

ACP

ACP-003

to be reviewed

Testable

1

0

The Home Community ID must be an Object Identifier (OID), using the urn format (that is, urn:oid: appended with the OID).

12

Section 3.1

5/24/17 8:53:48 AM by aberge

ACP

ACP-004

to be reviewed

Testable

1

0

Document Class must be a Document Class code defined in the NHIN document metadata specifications. These are LOINC codes

12

Section 3.1

5/24/17 8:54:01 AM by aberge

ACP

ACP-005

to be reviewed

Testable

1

0

The User ID must be specified as either an e-mail address (rfc822Name) or an X500 name (x500Name)

12

Section 3.1

5/24/17 8:54:15 AM by aberge

ACP

ACP-006

to be reviewed

Testable

1

0

One of authorPerson or authorInstitution elements should be used to provide information about the author of the Access Consent Policy

13

Table 1

5/24/17 8:54:24 AM by aberge

ACP

ACP-007

to be reviewed

Testable

1

0

classCode must use the LOINC code 57017-6to represent Access Consent Policy. The description for this code is Privacy Policy.

13

Table 1

5/24/17 8:54:26 AM by aberge

ACP

ACP-008

to be reviewed

Testable

1

0

The value of the eventCodeList is an OID, which must be prefixed with urn:oid:. Since OIDs do not have a coding scheme, use the value N/A in the coding scheme slot

13

Table 1

5/24/17 8:54:32 AM by aberge

ACP

ACP-009

to be reviewed

Testable

1

0

Lack of serviceStartTime/serviceStopTime must be interpreted as meaning that the policy is not time limited

13

Table 1