Final2.16.840.1.113883.5.1100 - Acknowledgement Detail Code - FHIR: http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode
| Level/ Type | Code | Display Name | Code System | Description |
|---|---|---|---|---|
| 0‑L | NS200 | unsupported interaction | Acknowledgement Detail Code | The interaction (or: this version of the interaction) is not supported. |
| 0‑L | NS202 | unsupported processing id | Acknowledgement Detail Code | The Processing ID is not supported. |
| 0‑L | NS203 | unsupported version id | Acknowledgement Detail Code | The Version ID is not supported. |
| 0‑L | NS250 | unsupported processing Mode | Acknowledgement Detail Code | The processing mode is not supported. |
| 0‑L | NS260 | unknown sender | Acknowledgement Detail Code | The Device.id of the sender is unknown. |
| 0‑L | NS261 | unrecognized attentionline | Acknowledgement Detail Code | The receiver requires information in the attentionLine classes for routing purposes. |
| 0‑L | SYN100 | required association missing | Acknowledgement Detail Code | Required association missing in message; or the sequence of the classes is different than required by the standard or one of the conformance profiles identified in the message. |
| 0‑L | SYN101 | required attribute missing | Acknowledgement Detail Code | A required attribute is missing in a class. |
| 0‑L | SYN102 | data type error | Acknowledgement Detail Code | The attribute contained data of the wrong data type, e.g. a numeric attribute contained 'FOO'. |
| 0‑L | SYN103 | value not found in code system | Acknowledgement Detail Code | An attribute value was compared against the corresponding code system, and no match was found. |
| 0‑L | SYN104 | invalid code system in CNE | Acknowledgement Detail Code | An attribute value referenced a code system that is not valid for an attribute constrained to CNE. |
| 0‑L | SYN110 | number of association repetitions exceeds limit | Acknowledgement Detail Code | The number of repetitions of a (group of) association(s) exceeds the limits of the standard or of one of the conformance profiles identified in the message. |
| 0‑L | SYN112 | number of attribute repetitions exceeds limit | Acknowledgement Detail Code | The number of repetitions of an attribute exceeds the limits of the standard or of one of the conformance profiles identified in the message. |
| 0‑L | NOSTORE | no storage space for message. | Acknowledgement Detail Code | Rejection: The message can't be stored by the receiver due to an unspecified internal application issue. The message was neither processed nor stored by the receiving application. |
| 0‑L | RTEDEST | message routing error, destination unreachable. | Acknowledgement Detail Code | Error: The destination of this message is known to the receiving application. Messages have been successfully routed to that destination in the past. The link to the destination application or an intermediate application is unavailable. |
| 0‑L | RTUDEST | error: message routing error, unknown destination. | Acknowledgement Detail Code | The destination of this message is unknown to the receiving application. The receiving application in the message does not match the application which received the message. The message was neither routed, processed nor stored by the receiving application. |
| 0‑L | RTWDEST | message routing warning, destination unreachable. | Acknowledgement Detail Code | Warning: The destination of this message is known to the receiving application. Messages have been successfully routed to that destination in the past. The link to the destination application or an intermediate application is (temporarily) unavailable. The receiving application will forward the message as soon as the destination can be reached again. |
| 0‑L | PGNE | Placer Group Number Error | Acknowledgement Detail Code | 'The format of the patient identifier does not match the specification for the indicated patient identifier type.' |
| 0‑L | INVPDOB | Invalid Patient Date of Birth | Acknowledgement Detail Code | The Patient's date of birth must not be in the future and must not be more than 130 years in the past. |
| 0‑L | INVTRQDT | Invalid Test Request Date | Acknowledgement Detail Code | 'The test request date must be no more than six months in the past, and no more than thirteen months in the future.' |
| 0‑L | INCTRQST | Incorrect Test Request Status | Acknowledgement Detail Code | 'The test request status indicated in the message is not valid for the test request.' |
| 0‑L | TRQMIS | Test Request Status/Value Mismatch | Acknowledgement Detail Code | 'A test result value was provided with a test result status of ‘X’, or a value was not provided and the test result status is not ‘X’.' |
| 0‑L | INVSPECCOLDT | Invalid Specimen Collection Date | Acknowledgement Detail Code | 'The specimen collection date/time must not be in the future.' |
| 0‑L | PIDMIS | Patient Identifier Mismatch | Acknowledgement Detail Code | 'None of the patient identifiers in the message match a patient identifier on the existing order.' |
| 0‑L | CLVALRTAV | Clinically Valid Result Available | Acknowledgement Detail Code | 'A clinically valid result exists in JLIS for the test being ordered. ' |
| 0‑L | PNOTAUTH | Practitioner Not Authorized to Order Test | Acknowledgement Detail Code | practitioner type. The indicated ordering |
| 0‑L | LABNOTAUTH | Laboratory Not Authorized to Perform Test | Acknowledgement Detail Code | 'The test that can be performed vary by laboratory. The indicated performing laboratory is not licensed to perform the indicated test.' |
| 0‑L | PHNNOF | PHN does not exist in the ECR | Acknowledgement Detail Code | The patient identifier (PHN) provided in the message does not match an identifier existing in the Client Registry. |
| 0‑L | MRNNOF | MRN does not exist in the ECR | Acknowledgement Detail Code | The patient identifier (MRN) provided in the message does not match an identifier existing in the Client Registry. |
| 0‑L | MRNNOPHN | MRN does not resolve to a PHN in the ECR | Acknowledgement Detail Code | The patient identifier (MRN) exists in the Client Registry but a PHN has not been assigned. |
| 0‑L | PHNDEP | Personal Health Number has been deprecated. | Acknowledgement Detail Code | The Patient Healthcare identifier (BC PHN) has been replaced due to a merge. The identifier provided in the message has been superceded. |
| 0‑L | MRNDEP | MRN patient Identifier has been deprecated. | Acknowledgement Detail Code | The Patient identifier (MRN) has been replaced due to a merge. The identifier provided in the message has been superceded. |
| 0‑L | PIDNOTAUTH | Non-authorized source identifier | Acknowledgement Detail Code | A patient identifier has been provided but the source (assigning authority) is a non-authorized source of registered patient identifiers. |
| 0‑L | PIDDEMMIS | Patient ID - Demographics mismatch | Acknowledgement Detail Code | Supplied patient demographics do not match the demographics recorded in the Client Registry for the primary identiifer supplied in the message. |
| 0‑L | PRNOF | Ordering provider does not exist | Acknowledgement Detail Code | The Ordering Provider identified in the message does not exist in the Provider Registry |
| 0‑L | PRDEMMIS | Ordering Provider Id - Demographics mismatch. | Acknowledgement Detail Code | Supplied provider demographics do not match the demographics recorded in the Provider Registry for the identifier supplied in the message. |
| 0‑L | RECNOF | iEHR Distribution target is not a user of the system. | Acknowledgement Detail Code | A receiver identified on the iEHR Distribution List is not a user of the system. |
| 0‑L | RECINC | iEHR Distribution target does not have an endpoint designated within the iEHR solution | Acknowledgement Detail Code | A receiver identified on the iEHR Distribution List has no endpoint defined for report distribution. |
| 0‑L | RECINACT | Endpoint for an iEHR Distribution target is not enabled. | Acknowledgement Detail Code | A receiver identified on the iEHR Distribution List has a disabled endpoint. |
| 0‑L | BADMSG | Message Corrupt | Acknowledgement Detail Code | The PLIS Domain is unable to store the results message in the repository. |
| 0‑L | SFXDATINC | Sending Facility Cross-reference Data incomplete | Acknowledgement Detail Code | the Sending Facility cannot be found in the Sending Facility cross reference data, or if required information is not present for a Sending Facility |
| 0‑L | LOINCTYPE1 | Observation result code is the wrong type | Acknowledgement Detail Code | the Observation code is not a resultable code ('R' or 'B') |
| 0‑L | LOINCTYPE2 | Ordered code is the wrong type. | Acknowledgement Detail Code | the Ordered test is not an orderable code (“O” or “B”). |
| 0‑L | SEQXDATNOG | Sequence cross-reference data missing. | Acknowledgement Detail Code | a Concatenated Value, or a Battery does not exist in the Sequence Cross-Reference data. |
| 0‑L | SEQXDATINC | Sequence cross-reference data incomplete: Heading ID code or sequence without heading. | Acknowledgement Detail Code | a Concatenated Value or a Battery exists in the Sequence Cross-Reference data but a required field is missing (e.g. Heading ID Code, sequence within Heading) - Stored, warning issued, and message sent to Help Desk |
| 0‑L | HXDATNOF | Heading Cross-reference data missing. | Acknowledgement Detail Code | a Heading ID Code does not exist in the Heading Cross-Reference data - Stored, warning issued and message sent to Help Desk |
| 0‑L | SHXDATNOF | Sub-Heading cross-reference data missing. | Acknowledgement Detail Code | a Sub-Heading ID Code does not exist in the Sub-Heading Cross-Reference data - Stored, warning issued and message sent to Help Desk |
| 0‑L | MICINC | Microbiology culture grid data incomplete. | Acknowledgement Detail Code | For the Microbiology Grid Creation, if any of the Concatenated Values are not identified as an Organism or an Antibiotic. |
