Global: ^WV(790.9

FileMan FileNo	FileMan Filename	Package
790.9	WV PREGNANCY/LACTATION STATUS CONFLICT EVENTS	Womens Health

FileMan FileNo

FileMan Filename

Package

790.9

WV PREGNANCY/LACTATION STATUS CONFLICT EVENTS

Womens Health

Description

The pregnancy and lactation status of a patient are stored in up to four different locations within VistA: the women's health package (data was obtained verbally from the patient), the laboratory package (a pregnancy test was resulted), the patient care encounter (PCE) package (a diagnosis or procedure code was recorded that indicates the patient's pregnancy or lactation status) and the registration package (a diagnosis or procedure code was recorded that indicates the patient's pregnancy or lactation status). To ensure that all four packages are in agreement as to the patient's current pregnancy or lactation status, the laboratory, PCE and registration packages are monitored for changes. When a conflict is identified, a Computerized Patient Record System (CPRS) notification is generated that when processed, allows the recipient to update the appropriate status in the women's health package. This file stores the events that triggered that status conflict notification. APPLICATION GROUP(S): WV

Package	Total	Routines
Womens Health	4	^WV(791 WVRPCPT1 ^WV(790.9 WVRPCPT2

Package

Total

Routines

Womens Health

^WV(791 WVRPCPT1 ^WV(790.9 WVRPCPT2

Package	Total	Routines
Womens Health	1	WVRPCPT1

Package

Total

Routines

Womens Health

WVRPCPT1

Package	Total	FileMan Files
Registration	1	PATIENT(#2)[2]

Package

Total

FileMan Files

Registration

PATIENT(#2)[2]

Fields, Total: 7

Field #	Name	Loc	Type	Details
.01	DATE/TIME OCCURRED	0;1	DATE	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `S %DT="ESTXR" D ^%DT S X=Y K:X<1 X` LAST EDITED: `OCT 08, 2019` HELP-PROMPT: `Enter the date and time of the event that caused the status conflict.` DESCRIPTION: `This field stores the date and time the event occurred.` CROSS-REFERENCE: `790.9^B` `1)= S ^WV(790.9,"B",$E(X,1,30),DA)=""` `2)= K ^WV(790.9,"B",$E(X,1,30),DA)`
2	PATIENT	0;2	POINTER TO PATIENT FILE (#2)	PATIENT(#2) INPUT TRANSFORM: `I +X>0,$P($G(^DPT(X,0)),U,2)'="F" K X D EN^DDIOL("Patient is not female.")` LAST EDITED: `DEC 03, 2020` HELP-PROMPT: `Select the female patient associated with this event.` DESCRIPTION: `This field stores the patient associated with the event.` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` RECORD INDEXES: `AC (#1594), C (#1595)`
3	STATUS TYPE	0;3	SET	'P' FOR PREGNANCY; 'L' FOR LACTATION; LAST EDITED: `DEC 03, 2020` HELP-PROMPT: `Select the type of status associated with this event.` DESCRIPTION: `This field stores the type of status associated with the event.` RECORD INDEXES: `AC (#1594)`
4	CODING SYSTEM	0;4	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>7!($L(X)<3) X` `MAXIMUM LENGTH: 7` LAST EDITED: `OCT 08, 2019` HELP-PROMPT: `Enter the coding system from which the code that generated this event comes from, 3-7 characters in length.` DESCRIPTION: `This is the coding system that contains the code that generated this event.` RECORD INDEXES: `C (#1595)`
5	CODE	0;5	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>40!($L(X)<1) X` `MAXIMUM LENGTH: 40` LAST EDITED: `OCT 08, 2019` HELP-PROMPT: `Enter the code that generated this event, 1-40 characters in length.` DESCRIPTION: `This is the code that generated this event.` RECORD INDEXES: `C (#1595)`
6	DATE OF INTEREST	0;6	DATE	INPUT TRANSFORM: `S %DT="E" D ^%DT S X=Y K:X<1 X` LAST EDITED: `OCT 08, 2019` HELP-PROMPT: `Enter the date that should be used when resolving the CODING SYSTEM and CODE field values.` DESCRIPTION: `This is the date used to resolve the CODING SYSTEM (#4) and CODE (#5) fields, irrespective of code set versions.` RECORD INDEXES: `C (#1595)`
10	DESCRIPTION	1;0	WORD-PROCESSING #790.9001	DESCRIPTION: `This field stores the text that is displayed to the user who processes the status conflict notification. This text is a description of the data that is in conflict (for example, the name of the pregnancy test, the date it` `was resulted on and the result of the test).` LAST EDITED: `JUN 12, 2017` HELP-PROMPT: `Describe the event that caused the status conflict, such as details about the laboratory test or encounter code.` DESCRIPTION: `This field stores the text that is displayed to the user who processes the status conflict notification. This text is a description of the data that is in conflict (for example, the name of the pregnancy test, the date` `it was resulted on and the result of the test).`

Name	Field # of Occurrence
^%DT	.01+1, 6+1
EN^DDIOL	2+1
Y^DIQ	ID2+1

Name

Field # of Occurrence

^%DT

.01+1, 6+1

EN^DDIOL

2+1

Y^DIQ

ID2+1

Name	Line Occurrences (* Changed, ! Killed)
^DD(2	ID2+1
^DPT - [#2]	ID2+1, 2+1
^WV(790.9 - [#790.9]	IXACSL+1, IXACKL+1!, IXACKEIC+1!, IXCSL+1, IXCKL+1!, IXCKEIC+1!, .01(XREF 1S), .01(XREF 1K)

Name

Line Occurrences (* Changed, ! Killed)

^DD(2

ID2+1

^DPT - [#2]

ID2+1, 2+1

^WV(790.9 - [#790.9]

IXACSL+1*, IXACKL+1!, IXACKEIC+1!, IXCSL+1*, IXCKL+1!, IXCKEIC+1!, .01(XREF 1S), .01(XREF 1K)

Name	Field # of Occurrence
^(0	ID2+1

Name

Field # of Occurrence

^(0

ID2+1

Local Variables

Legend:

>>	Not killed explicitly
*	Changed
!	Killed
~	Newed

Name	Field # of Occurrence
>> %DT	.01+1, 6+1
%I	ID2+1*!
>> C	ID2+1*
>> DA	IXACSL+1, IXACKL+1, IXCSL+1, IXCKL+1, .01(XREF 1S), .01(XREF 1K)
>> DIC	ID2+1, ID3+1
U	ID2+1, 2+1
X	IXCP2TS+1, .01+1!, .01(XREF 1S), .01(XREF 1K), 2+1!, 4+1!, 5+1!, 6+1*!
X(1	IXACSL+1, IXACKL+1, IXCSL+1, IXCKL+1
X(2	IXACSL+1, IXACKL+1, IXCSL+1, IXCKL+1
X(3	IXCSL+1, IXCKL+1
X(4	IXCSL+1, IXCKL+1
>> Y	ID2+1*, .01+1, 6+1

Customize PDF page

Package: Womens Health

Global: ^WV(790.9

Information

Description

Directly Accessed By Routines, Total: 4

Accessed By FileMan Db Calls, Total: 1

Pointer To FileMan Files, Total: 1

Fields, Total: 7

External References

Global Variables Directly Accessed

Naked Globals

Local Variables

Legend: