Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.1100 HL7 v3 Code System AcknowledgementDetailCode

Vocabulary Work Group Maturity Level: N/A External Use Context: Any

This code system (http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode) is defined as part of HL7 v3.

Summary

Defining URL: http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode

Version: 2018年08月12日

Name: v3.AcknowledgementDetailCode

Title: v3 Code System AcknowledgementDetailCode

Definition:

OpenIssue: Missing description.

OID: 2.16.840.1.113883.5.1100 (for OID based terminology systems)

Source Resource XML / JSON

This Code system is used in the following value sets:

ValueSet: v3 Code System AcknowledgementDetailCode ( OpenIssue: Missing description.)

4.4.2.1100.1 Code System Content

Release Date: 2018年08月12日

Level Code Display Definition

1 (_AcknowledgementDetailNotSupportedCode) Abstract Refelects rejections because elements of the communication are not supported in the current context.

2 NS200 Unsupported interaction The interaction (or: this version of the interaction) is not supported.

2 NS202 Unsupported processing id The Processing ID is not supported.

2 NS203 Unsupported version id The Version ID is not supported.

2 NS250 Unsupported processing Mode The processing mode is not supported.

2 NS260 Unknown sender The Device.id of the sender is unknown.

2 NS261 Unrecognized attentionline The receiver requires information in the attentionLine classes for routing purposes.

1 INTERR Internal system error An internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message.

1 NOSTORE No storage space for message. 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.

1 RTEDEST Message routing error, destination unreachable. 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.

1 RTUDEST Error: Message routing error, unknown destination. 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.

1 RTWDEST Message routing warning, destination unreachable. 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.

1 SYN Syntax error Reflects errors in the syntax or structure of the communication.

2 SYN102 Data type error The attribute contained data of the wrong data type, e.g. a numeric attribute contained "FOO".

2 SYN105 Required element missing Description: Required association or attribute 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.

3 SYN100 Required association missing 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.

3 SYN101 Required attribute missing A required attribute is missing in a class.

3 SYN114 Insufficient repetitions Description: The number of repetitions of a group of association or attributes is less than the required minimum for the standard or of one of the conformance profiles or templates identified in the message.

2 SYN106 Terminology error Description: A coded attribute or datatype property violates one of the terminology constraints specified in the standard or one of the conformance profiles or templates declared by the instance.

3 SYN103 Value not found in code system An attribute value was compared against the corresponding code system, and no match was found.

3 SYN104 Invalid code system in CNE An attribute value referenced a code system that is not valid for an attribute constrained to CNE.

3 SYN107 Deprecated code Description: A coded attribute is referencing a code that has been deprecated by the owning code system.

2 SYN108 Number of repetitions exceeds limit Description: The number of repetitions of a (group of) association(s) or attribute(s) exceeds the limits of the standard or of one of the conformance profiles or templates identified in the message.

3 SYN110 Number of association repetitions exceeds limit 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.

3 SYN112 Number of attribute repetitions exceeds limit The number of repetitions of an attribute exceeds the limits of the standard or of one of the conformance profiles identified in the message.

2 SYN109 Mandatory element with null value Description: An attribute or association identified as mandatory in a specification or declared conformance profile or template has been specified with a null flavor.

2 SYN111 Value does not match fixed value Description: The value of an attribute or property differs from the fixed value asserted in the standard or one of the conformance profiles or templates declared in the message.

2 SYN113 Formal constraint violation Description: A formal constraint asserted in the standard or one of the conformance profiles or templates declared in the message has been violated.