The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

DPS - Diagnosis And Procedure Code Segment

The Technical Steward for the DPS segment is Orders and Observations.

For the payer defined in PM1-1 and the service provider defined in MFE-4 and the Producer's Service/Test/Observation ID in MCP-2 these are the Diagnosis and Procedure that impact coverage requirements as defined by:

HL7 Attribute Table - DPS - Diagnosis and Procedure Code Segment
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
DPS
1 03472 Diagnosis Code - MCP SHALL [1..1] CWE
2 03484 Procedure Code SHALL [1..*] CWE
3 00662 Effective Date/Time [0..1] DTM
4 03473 Expiration Date/Time [0..1] DTM
5 03474 Type of Limitation [0..1] CNE

DPS-1: Diagnosis Code - MCP (CWE) 03472

Definition: DPS-1 contains the diagnosis code assigned to this diagnosis. Refer to User-defined Table 0051 - Diagnosis Code for suggested values. This field is a CWE data type for compatibility with clinical and ancillary systems. Either DPS-1.1-Identifier or DPS-1.2-Text is required. When a code is used in DPS-1.1-Identifier, a coding system is required in DPS-1.3-Name of Coding System.

Names of various diagnosis coding systems are listed in Chapter 2, Section 2.16.4, “Coding system table.”

DPS-2: Procedure Code (CWE) 03484

Definition: This field contains the procedure code for procedure, if any, associated with this charge description. Repeating field allows for different procedure coding systems such as CPT4, ASTM, ICD9. Coded entry made up of code plus coding schema. See Externally Defined Table 0941 – Procedure Code.

DPS-3: Effective Date/Time (DTM) 00662

(Definition from MFI.5 in Ch. 8)

Definition: This optional field contains the effective date/time, which can be included for file-level action specified. It is the date/time the originating system expects that the event is to have been completed on the receiving system. If this field is not present, the action date/time should default to the current date/time (when the message is received).

(Definition from MFE.3 in Ch. 8)

Definition: An optional effective date/time can be included for the record-level action specified. It is the date/time the originating system expects that the event is to have been completed on the receiving system. If this field is not present, the effective date/time should default to the current date/time (when the message is received).

(Definition from DPS.3 in Ch. 8)

Definition: An optional effective date/time can be included for the record-level action specified. It is the date/time the originating system expects that the event is to have been completed on the receiving system. If this field is not present, the effective date/time should default to the current date/time (when the message is received).

DPS-4: Expiration Date/Time (DTM) 03473

Definition: An optional expiration date/time can be included for the record-level action specified. It is the date/time the originating system expects that the event is to have been completed on the receiving system.

DPS-5: Type of Limitation (CNE) 03474

Definition: This field contains the type of limitations as determined by the Payer. This field has a defined value set that may need to be extended. See HL7 Table 0940 - Limitation Type Codes, in Chapter 2C, Code Tables for valid values.