Add error code text per CP #1.

CPs/IHE_DEV_Suppl_PCIM_Foundational CP applied.adoc

@@ -576,6 +576,15 @@ On receipt of the message, the manager system checks for valid syntax and that t
 
 After these checks, the Manager logs the result and returns an appropriate positive or negative commit-level acknowledgement to the Reporter. If a positive commit-level acknowledgement is sent, an application-level acknowledgment may be sent to the Reporter after the association or disassociation is validated at the Manager (Additional detail on  application acknowledgement semantics is forthcoming). The system design must assure that errors are indicated to the appropriate human user(s) in an effective and timely manner so that action can be taken. In this case, a technical alert should be raised using the ACM profile, the details of this are out of scope for this document. 
 
+Examples of errors that can occur during device patient association processing include the following:
+
+[.text-left]
+
+*  Device specified by the Reporter is unknown to the Manager. 
+*  An association request is received by the Manager, but the specified device is associated with another patient.
+*  Specified patient is unknown.
+*  An internal error prevents the Manager from fulfilling the request. 
+
 If the checks are passed, the Manager establishes a record of the beginning or ending of the association and the effective time.
 
 == Report Association State [DEV-52]
@@ -1344,6 +1353,56 @@ Table A.1.3-1: Communicate Device-Patient Association - Application Acknowledgem
 
 |===
 
+The list of error codes that can occur during the processing of DEV-51 messages are listed below. The application acknowledgment sent by the Device-Patient Association Manager should contain the Code and Text in ERR-5.1 and ERR-5.2 respectively. ERR-5.9 can also be used to contain additional text related to the error.
+
+[.text-left]
+_Note that the definition of the range of error codes available for use by this profile is TBD. It is assumed that error codes will start at the lower limit of the range and be incremented by one as new error codes are added._ 
+
+[cols="2,3,4",options=header]
+|===
+
+|Code
+|Text
+|Example
+
+|_Lower limit + 1_
+|Other error
+|Used when other errors are not applicable.
+
+|_Lower limit + 2_
+|Unknown device
+|Specified device is unknown.
+
+|_Lower limit + 3_
+|Unknown patient
+|Specified patient is unknown.
+
+|_Lower limit + 4_
+|Device is associated with another patient
+|A device-patient association or disassociation request was received, but the device specified in the request is associated with a different patient.
+
+|_Lower limit + 5_
+|Device is not associated with a patient
+|A device-patient disassociation request was received, but the device specified in the request is not associated with a patient.
+
+|_Lower limit + 6_
+|Unknown location
+|Specified location is unknown.
+
+|_Lower limit + 7_
+|Device-Patient association rejected.
+|Device-Patient Association Reporter sent an unvalidated Device-Patient association request (OBX-11 is not equal to \‘F\’). Association request was rejected by the participating user.
+
+|_Lower limit + 8_
+|User is unauthorized.
+|Participating user is unauthorized to perform request.
+
+|_Lower limit + 9_
+|Unknown user
+|Participating user is not known by the Device-Patient Association Manager.
+
+|===
+
 == A.2 Filter Associations Message
 
 === A.2.1 Scope