Sub-Field: 375.04

Parent File	Name	Number	Package
PFSS ACCOUNT(#375)	DIAGNOSIS	375.04	Integrated Billing

Details

Field # Name Loc Type Details

Field #	Name	Loc	Type	Details
.01	SET ID	0;1	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `JUN 27, 2005` HELP-PROMPT: `Type a Number between 1 and 99, 0 Decimal Digits` DESCRIPTION: `Unique, sequential integer. The Diagnosis with SET ID=1 should be interpreted as the Primary Diagnosis.` `Each application sending account data to IBB may provide one or more related diagnoses. If more than one, then these diagnoses are passed to IBB in priority order; i.e., the first diagnosis is the primary diagnosis` `related to the charge, the second diagnosis is the secondary diagnosis related to the charge, etc. IBB files the data into subfile #375.04 in that same order. This field indicates the exact order in which the diagnoses` `were received and filed.` CROSS-REFERENCE: `375.04^B` `1)= S ^IBBAA(375,DA(1),"DG1","B",$E(X,1,30),DA)=""` `2)= K ^IBBAA(375,DA(1),"DG1","B",$E(X,1,30),DA)`
.03	DIAGNOSIS CODE	0;3	POINTER TO ICD DIAGNOSIS FILE (#80)	**********************REQUIRED FIELD********************** ICD DIAGNOSIS(#80) LAST EDITED: `FEB 24, 2005` DESCRIPTION: `The applications sending account data to IBB may provide one or more related diagnoses. Each diagnosis is provided as a pointer to the ICD DIAGNOSIS file (#80).` TECHNICAL DESCR: `PFSS HL7 ADT message data; DG1 Segment, Sequence 3.`
.06	DIAGNOSIS TYPE	0;6	SET	**********************REQUIRED FIELD********************** 'A' FOR ADMITTING; 'D' FOR DISCHARGE; 'W' FOR WORKING; 'F' FOR FINAL; LAST EDITED: `APR 20, 2005` DESCRIPTION: `The applications passing account data to IBB must define each diagnosis code included in the charge data as being one of the following: A(dmitting), W(orking), D(ischarging), or F(inal).` TECHNICAL DESCR: `PFSS HL7 ADT message data; DG1 Segment, Sequence 6.`

.01

SET ID

0;1

NUMBER

INPUT TRANSFORM: K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: JUN 27, 2005
HELP-PROMPT: Type a Number between 1 and 99, 0 Decimal Digits
DESCRIPTION: Unique, sequential integer. The Diagnosis with SET ID=1 should be interpreted as the Primary Diagnosis.
Each application sending account data to IBB may provide one or more related diagnoses. If more than one, then these diagnoses are passed to IBB in priority order; i.e., the first diagnosis is the primary diagnosis
related to the charge, the second diagnosis is the secondary diagnosis related to the charge, etc. IBB files the data into subfile #375.04 in that same order. This field indicates the exact order in which the diagnoses
were received and filed.
CROSS-REFERENCE: 375.04^B
1)= S ^IBBAA(375,DA(1),"DG1","B",$E(X,1,30),DA)=""
2)= K ^IBBAA(375,DA(1),"DG1","B",$E(X,1,30),DA)

.03

DIAGNOSIS CODE

0;3

POINTER TO ICD DIAGNOSIS FILE (#80)

************************REQUIRED FIELD************************

ICD DIAGNOSIS(#80)

LAST EDITED: FEB 24, 2005
DESCRIPTION:
The applications sending account data to IBB may provide one or more related diagnoses. Each diagnosis is provided as a pointer to the ICD DIAGNOSIS file (#80).
TECHNICAL DESCR:
PFSS HL7 ADT message data; DG1 Segment, Sequence 3.

.06

DIAGNOSIS TYPE

0;6

SET

************************REQUIRED FIELD************************

'A' FOR ADMITTING;
'D' FOR DISCHARGE;
'W' FOR WORKING;
'F' FOR FINAL;

LAST EDITED: APR 20, 2005
DESCRIPTION:
The applications passing account data to IBB must define each diagnosis code included in the charge data as being one of the following: A(dmitting), W(orking), D(ischarging), or F(inal).
TECHNICAL DESCR:
PFSS HL7 ADT message data; DG1 Segment, Sequence 6.

Customize PDF page

Package: Integrated Billing

PFSS ACCOUNT(#375)-->375.04

Sub-Field: 375.04

Information

Details