DICOM PS3.4 2018e - Service Class Specifications

P.3.2.3 Service Class Provider Behavior (Current)
Prev | P.3.2 Operation | Next

#### P.3.2.3 Service Class Provider Behavior

The SCP shall receive, via the N-ACTION request primitive, requests for logging of substance administration events. The SCP shall incorporate those event records into a Medication Administration Record or similar log for the specified Patient.

### Note

The patient's identify may be conveyed explicitly by Patient ID (0010,0020), or implicitly by Admission (i.e., Visit) ID (0038,0010). An institution may typically chose one or the other to use as the primary patient identifier at the point of care, e.g., printed on a bar coded wristband, the use of which may facilitate data entry for the log entry. However, in the "Model of the Real World for the Purpose of Modality-IS Interface" (see PS3.3), the Visit is subsidiary to the Patient; hence the Admission ID (0038,0010) may only be unique within the context of the patient, not within the context of the institution. The use of the Admission ID (0038,0010) Attribute to identify the Patient is only effective if the Admission ID (0038,0010) is unique within the context of the institution.

The SCP shall support inclusion into the Medication Administration Record or similar log of values of all Type 1 and Type 2 Attributes for which the SCU has provided values. The SCP may convert these Attributes into a form appropriate for the destination log.

### Note

The SCP may convert coded data to free text in the log, with loss of the specific code values, if the log does not support such coded data.

The SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated action request.

Prev | Up | Next
P.3.2.2 Service Class User Behavior | Home | P.3.2.4 Status Codes

DICOM PS3.4 2018e - Service Class Specifications