Extensions for Using Data Elements from FHIR R4 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4-v3-AcknowledgementDetailCode-for-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Responsible: HL7 International / Terminology Infrastructure | Computable Name: R4V3AcknowledgementDetailCodeForR4B | |
This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailCode|2018-08-12 for use in FHIR R4B.
This value set is part of the cross-version definitions generated to enable use of the
value set http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailCode|2018-08-12 as defined in FHIR R4
in FHIR R4B.
The source value set is bound to the following FHIR R4 elements:
Note that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailCode|2018-08-12, defined in FHIR R4 does not have any mapping to FHIR R4B
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode version 📍2018-08-12| Code | Display | Definition |
| INTERR | Internal system error | An internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message. |
| 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. |
| NS200 | Unsupported interaction | The interaction (or: this version of the interaction) is not supported. |
| NS202 | Unsupported processing id | The Processing ID is not supported. |
| NS203 | Unsupported version id | The Version ID is not supported. |
| NS250 | Unsupported processing Mode | The processing mode is not supported. |
| NS260 | Unknown sender | The Device.id of the sender is unknown. |
| NS261 | Unrecognized attentionline | The receiver requires information in the attentionLine classes for routing purposes. |
| 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. |
| 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. |
| 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. |
| SYN | Syntax error | Reflects errors in the syntax or structure of the communication. |
| 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. |
| SYN101 | Required attribute missing | A required attribute is missing in a class. |
| SYN102 | Data type error | The attribute contained data of the wrong data type, e.g. a numeric attribute contained "FOO". |
| SYN103 | Value not found in code system | An attribute value was compared against the corresponding code system, and no match was found. |
| SYN104 | Invalid code system in CNE | An attribute value referenced a code system that is not valid for an attribute constrained to CNE. |
| 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. |
| 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. |
| SYN107 | Deprecated code | Description: A coded attribute is referencing a code that has been deprecated by the owning code system. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| _AcknowledgementDetailNotSupportedCode | AcknowledgementDetailNotSupportedCode | Refelects rejections because elements of the communication are not supported in the current context. |
This value set expansion contains 28 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | INTERR | Internal system error | An internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | NS200 | Unsupported interaction | The interaction (or: this version of the interaction) is not supported. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | NS202 | Unsupported processing id | The Processing ID is not supported. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | NS203 | Unsupported version id | The Version ID is not supported. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | NS250 | Unsupported processing Mode | The processing mode is not supported. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | NS260 | Unknown sender | The Device.id of the sender is unknown. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | NS261 | Unrecognized attentionline | The receiver requires information in the attentionLine classes for routing purposes. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | SYN | Syntax error | Reflects errors in the syntax or structure of the communication. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | SYN101 | Required attribute missing | A required attribute is missing in a class. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | SYN102 | Data type error | The attribute contained data of the wrong data type, e.g. a numeric attribute contained "FOO". | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | SYN103 | Value not found in code system | An attribute value was compared against the corresponding code system, and no match was found. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | SYN104 | Invalid code system in CNE | An attribute value referenced a code system that is not valid for an attribute constrained to CNE. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | SYN107 | Deprecated code | Description: A coded attribute is referencing a code that has been deprecated by the owning code system. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | 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. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | 2018-08-12 | _AcknowledgementDetailNotSupportedCode | AcknowledgementDetailNotSupportedCode | Refelects rejections because elements of the communication are not supported in the current context. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |