Global: ^PXRMXT(810.3

FileMan FileNo	FileMan Filename	Package
810.3	REMINDER EXTRACT SUMMARY	Clinical Reminders

Description

This file stores compliance totals found for a specific extract. The extract Entries are read only and may be selected by number or extract name. The extract Summary entries are currently created from two types of processing: 1) Generic EXTRACT tool manual runs and automated runs 2) LREPI ENHANCE MANUAL RUN and LREPI NIGHTLY TASK on day 15 of each month Generic extract summary entries: The REMINDER EXTRACT SUMMARY NAME is the combination of a unique abbreviation. When the extract is created from the EXTRACT manual and automated options, the REMINDER EXTRACT SUMMARY NAME will include Q, M, or Y (for quarterly, monthly, or yearly), nn for month or quarter, and yyyy for year. The following is an example of extract names: VA-IHD QUERI 2006 M2 VA-IHD QUERI 2006 M1 VA-IHD QUERI 2005 M12 National extract summary entries created from generic Reminder Extract functionality (not LREPI) are stored with a VA- prefixed name. Each extract entry contains reminder compliance totals for each unique combination of patient list and reminder. The extract will optionally store finding compliance totals if the TYPE OF TOTALS for the extract is "Compliance and Finding Totals". No patient specific data is stored in the extract summary file for generic extracts. The patient lists (denominators) used to create the extract summary totals, for a particular reporting period, are available from Reminder Patient List options. Generic extract summary entries will default to be purged after 5 years. The automated purge status can be changed for a particular extract summary entry to retain the entry indefinitely. LREPI extract summary entries: The LREPI extract names use YY/MM representing the ending year and month of the extract date range, and the run date in the format YYMMDD. The date and time of the run is an identifier. The following is an example of LREPI extract names. LREPI 00/05 061500 LREPI 00/06 073100 LREPI 00/07 081500 The LREPI extract entries assume all results are for the primary institution, and includes patient specific data with findings. The LREPI extracts created are based on LREPI reporting criteria which is not available for generic reporting functionality. This file will maintain up to 36 extract entries for each type of extract. After 36 entries, when a new entry is added, the oldest entry is deleted from the file. Sites are asked to run the LREPI ENHANCE MANUAL RUN for months starting from 10/01/98 through 8/31/00. This will seed the Emerging Pathogens Initiative (EPI) database with risk assessment data. Subsequent updates to the EPI database will automatically occur monthly via the LREPI NIGHTLY TASK option. Sites will have up to 36 months of extracts. This may be fewer than 36 months if the site runs extracts for the same month more than once. Multiple extracts for the same month occur when the site runs the LREPI ENHANCE MANUAL RUN for a month to fix errors found by the receiving national database. For LREPI runs, the receiving national database is the Emerging Pathogens Initiative (EPI) at the Austin Automation Center (AAC). An LREPI entry in the REMINDER EXTRACT SUMMARY file contains information that identifies the extract entry, the extract findings, and totals by finding item. The extract entry information includes the number, extract name, beginning and ending extract dates, person who ran the extract option, task number, total patients evaluated and total patients with findings. The extract findings include a number (for ease of selecting a finding item), patient, reminder term, value, alternate id, finding date, related visit (if PCE data), encounter type (I/O), result, value, drug and DSUP (days supply). These extract finding fields are returned by the reminder evaluation logic. The result, value, and drug are all free text fields without specific input and output transforms because the data comes from the source VistA data it came from, with read only access on this file. The alternate id is specific to the LREPI extracts. A number value in the alternate id field indicates that the finding is for Hepatitis C risk assessment. The alternate id will be used for statistical purposes in the EPI database. The flow of LREPI processing is as follows: 1) LREPI gathers Lab Search/Extract patients and findings 2) LREPI gets all patients and findings from a reminder extract evaluation process given the extract date range and reminder list. (The reminder list is from a new LREPI file 69.51). 2.1) The reminder extract evaluation logic uses medications mapped to reminder terms in the VA-NATIONAL EPI RX EXTRACT reminder, and the extract date range, to call new inpatient pharmacy and outpatient pharmacy extract logic to get patient pharmacy findings. 2.2) The reminder extract evaluation uses the remaining reminder criteria to build a list of patients with findings from the following files in the extract period: LAB DATA (#63) V POV (#9000010.07) V HEALTH FACTORS (#9000010.23) V PATIENT ED (#9000010.16) V EXAM (#9000010.13) 2.3) The list of patients is used to evaluate the VA-HEP C RISK ASSESSMENT and VA-NATIONAL EPI LAB EXTRACT reminders. The findings within the extract date range are added as Extract Findings in the REMINDER EXTRACT SUMMARY file and then returned to the Lab Search/Extract process. 3) The Lab Search/Extract process uses the final list of patients and findings to create HL7 messages. Each reminder finding for a patient is used to create a DSP segment. Pharmacy findings contain both a DSP and ZXE segment. 4) When the AAC processes the messages, error messages are returned for each message with the SSN related to the erroneous data. Note: Messages with errors are not added to the EPI database. When erroneous data is fixed at the site, the LREPI ENHANCE MANUAL RUN is run for the month with the error to transmit the entire month's data again. The new data for each patient and finding date replaces the old patient and finding date's data. 5) Two new options are available on the REMINDER REPORTS menu that provide total counts by finding item, as well as a detailed list by finding item and SSN. 6) Sites are encouraged to provide FileMan read-only access to the REMINDER EXTRACT SUMMARY file (810.3) for those who validate the extract data, the Hepatitis C implementation team, and Hepatitis C Coordinators responsible for monitoring Hepatitis C activities at each site.

Package	Total	Routines
Clinical Reminders	22	COMPLIANCE TOTALS EXTRACT FINDINGS FINDING TOTALS HL7 MESSAGE ID LREPI FINDING TOTALS PXRM EXTRACT EPI BY FIND_PT PXRM EXTRACT EPI TOTALS PXRM EXTRACT QUERI TOTALS PXRM7API PXRM7XT PXRMAPI1 PXRMETH PXRMETH1 PXRMETHL PXRMETT PXRMETX PXRMETXU PXRMP4I PXRMXXT UNIQUE APPLICABLE PATIENT LIST ^PXRMXT(810.3 PXRMXX1
Electronic Health Modernization	5	EHM-01158 EHM-01162 EHM-01448 EHM-01452 ^EHRM(1610
Kernel	1	^DIC(19

Package	Total	Routines
Clinical Reminders	4	PXRM7XT PXRMETXU PXRMGECL PXRMXX1

Package	Total	FileMan Files
Clinical Reminders	6	REMINDER TAXONOMY(#811.2)[#810.31(.04), #810.32(.01)] REMINDER DEFINITION(#811.9)[#810.33(.02)] REMINDER EXTRACT DEFINITION(#810.2)[1] REMINDER COMPUTED FINDINGS(#811.4)[#810.31(.04), #810.32(.01)] REMINDER TERM(#811.5)[#810.31(.03), #810.31(.04), #810.32(.01), #810.331(.02)] REMINDER PATIENT LIST(#810.5)[#810.33(.04)]
PCE Patient Care Encounter	6	VISIT(#9000010)[#810.31(.07)] EDUCATION TOPICS(#9999999.09)[#810.31(.04), #810.32(.01)] EXAM(#9999999.15)[#810.31(.04), #810.32(.01)] HEALTH FACTORS(#9999999.64)[#810.31(.04), #810.32(.01)] IMMUNIZATION(#9999999.14)[#810.31(.04), #810.32(.01)] SKIN TEST(#9999999.28)[#810.31(.04), #810.32(.01)]
Kernel	2	INSTITUTION(#4)[#810.33(.03)] NEW PERSON(#200)[.05]
National Drug File	2	VA DRUG CLASS(#50.605)[#810.31(.04), #810.32(.01)] VA GENERIC(#50.6)[#810.31(.04), #810.32(.01)]
General Medical Record - Vitals	1	GMRV VITAL TYPE(#120.51)[#810.31(.04), #810.32(.01)]
Lab Service	1	LABORATORY TEST(#60)[#810.31(.04), #810.32(.01)]
Mental Health	1	MH INSTRUMENT(#601)[#810.31(.04), #810.32(.01)]
Order Entry Results Reporting	1	ORDERABLE ITEMS(#101.43)[#810.31(.04), #810.32(.01)]
Pharmacy Data Management	1	DRUG(#50)[#810.31(.04), #810.32(.01)]
Radiology Nuclear Medicine	1	RAD/NUC MED PROCEDURES(#71)[#810.31(.04), #810.32(.01)]
Registration	1	PATIENT(#2)[#810.31(.01), #810.3316(.01)]

Fields, Total: 21

Field #	Name	Loc	Type	Details
.001	NUMBER		NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>9999999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `AUG 19, 2004` HELP-PROMPT: `Type a Number between 0 and 9999999, 0 Decimal Digits` DESCRIPTION: `This is the extract summary number.`
.01	NAME	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>64!($L(X)<3)!'(X'?1P.E) X` LAST EDITED: `MAY 04, 2006` HELP-PROMPT: `Answer must be 3-64 characters in length.` DESCRIPTION: `The NAME is the combination of a unique abbreviations for the type of extract. The file contains different extract types:` `1) EPI - Hep C Extract` `Extracts of this type are prefixed LREPI. The following is an example of EPI lookup information:` `LREPI 00/05 061500 LREPI 00/06 073100 LREPI 00/07 081500 The YY/MM represents the ending year and month of the extract date range, and the run date in the format YYMMDD. The date and` `time of the run is an identifier.` `2) VA- generic entries (IHD and MH QUERI)` `Extracts of this type are prefixed VA-IHD or VA-MH. The following is an example of IHD Look-up information:` `VA-IHD QUERI 2003 M2/01 VA-IHD QUERI 2003 M3/01 VA-IHD QUERI 2003 M4/01` `The reporting period of the extract run is included in the extract name. Since a particular reporting period can be rerun, each entry for the same reporting period is assigned a sequential entry number: /01 represents the` `first entry for the reporting period.` FIELD INDEX: `B (#506) REGULAR IR LOOKUP & SORTING` `Short Descr: "B" cross-reference for .01` `Set Logic: S ^PXRMXT(810.3,"B",$E(X,1,64),DA)=""` `Kill Logic: K ^PXRMXT(810.3,"B",$E(X,1,64),DA)` `Whole Kill: K ^PXRMXT(810.3,"B")` `X(1): NAME (810.3,.01) (Subscr 1) (Len 64) (forwards)`
.02	BEGINNING DATE	0;2	DATE	INPUT TRANSFORM: `S %DT="EX" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `JUL 08, 2000` HELP-PROMPT: `Enter the extract beginning date range.` DESCRIPTION: `This is the starting date that was used for the extract.`
.03	ENDING DATE	0;3	DATE	INPUT TRANSFORM: `S %DT="E" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `JUL 08, 2000` HELP-PROMPT: `Enter the extract ending date range.` DESCRIPTION: `This is the ending date that was used for the extract.`
.04	TASK #	0;4	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>10!($L(X)<3) X` LAST EDITED: `JUL 08, 2000` HELP-PROMPT: `Enter the task number of the job creating the extract.` DESCRIPTION: `This field identifies the task that was run to create the extract.`
.05	EXTRACT OWNER	0;5	POINTER TO NEW PERSON FILE (#200)	NEW PERSON(#200) LAST EDITED: `JUL 08, 2000` HELP-PROMPT: `Enter the person who ran the extract.` DESCRIPTION: `This is the person who ran the extract job.`
.06	EXTRACT DATE	0;6	DATE	INPUT TRANSFORM: `S %DT="ESTX" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `JUL 09, 2002` HELP-PROMPT: `Enter the date/time the extract entry was created.` DESCRIPTION: `This is the date/time that the extract entry was added to this file.` RECORD INDEXES: `C (#507)`
.07	PATIENTS EVALUATED	0;7	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>9999999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `JUL 09, 2000` HELP-PROMPT: `Enter the total count of patients with findings.` DESCRIPTION: `This is the total number of patients who had findings for the reminder and date range criteria selected.`
.08	PATIENTS WITH FINDINGS	0;8	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>9999999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `JUL 09, 2000` HELP-PROMPT: `Enter the number of findings extracted.` DESCRIPTION: `This is the total count of findings that met the extract criteria in the reminders and date range.`
1	EXTRACT DEFINITION	4;1	POINTER TO REMINDER EXTRACT DEFINITION FILE (#810.2)	REMINDER EXTRACT DEFINITION(#810.2) LAST EDITED: `MAY 04, 2006` DESCRIPTION: `This is a pointer to the EXTRACT DEFINITION file. This shows what extract was run to create this extract summary.` RECORD INDEXES: `C (#507), D (#508)`
2	TYPE OF TOTALS	4;2	SET	'CT' FOR COMPLIANCE TOTALS ONLY; 'CF' FOR COMPLIANCE AND FINDING TOTALS; LAST EDITED: `MAY 04, 2006` DESCRIPTION: `This is the type of totals requested for the extract parameter that was run to create this extract summary. An extract definition must contain Counting Rules in order for Finding Totals to be accumulated.`
3	REPORTING PERIOD	4;3	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>12)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `MAY 04, 2006` HELP-PROMPT: `Type a Number between 0 and 12, 0 Decimal Digits` DESCRIPTION: `This field is used to define the period of time that the extract was run. The period can be for a calendar Month or quarter.` RECORD INDEXES: `D (#508)`
4	REPORTING YEAR	4;4	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>2050)!(X<2000)!(X?.E1"."1N.N) X` LAST EDITED: `AUG 20, 2004` HELP-PROMPT: `Type a Number between 2000 and 2050, 0 Decimal Digits` DESCRIPTION: `This is for the year that the extract was run against.` RECORD INDEXES: `D (#508)`
5	MANUAL/AUTOSCHEDULED FLAG	4;5	SET	'M' FOR MANUAL; 'A' FOR AUTOSCHEDULED; LAST EDITED: `JUL 08, 2002` DESCRIPTION: `This field indicates if the extract summary was created from an autoscheduled extract or as the result of a manual run.`
6	HL7 MESSAGE ID	5;0	Multiple #810.36	810.36 DESCRIPTION: `This multiple contains each HL7 ID for every time this extract summary was transmitted to Austin.`
7	REPORT FREQUENCY	4;6	SET	'M' FOR MONTHLY; 'Q' FOR QUARTERLY; 'Y' FOR YEARLY; LAST EDITED: `OCT 01, 2002`
10	EXTRACT FINDINGS	1;0	POINTER Multiple #810.31	810.31 DESCRIPTION: `This is the LREPI patient findings found during reminder extract processing for the specified date range. Entries can be selected based on the NUMBER on the EXTRACT FINDINGS multiple or the Patient.`
20	LREPI FINDING TOTALS	2;0	VARIABLE POINTER Multiple #810.32	810.32 LAST EDITED: `MAY 04, 2006` DESCRIPTION: `This is the total count for each finding item extracted during LREPI processing..` TECHNICAL DESCR:
30	COMPLIANCE TOTALS	3;0	Multiple #810.33	810.33 LAST EDITED: `JUN 20, 2002` DESCRIPTION: `Used for Generic Extract reporting.` TECHNICAL DESCR: IDENTIFIED BY: `REMINDER(#.02), STATION(#.03)`
50	AUTOMATICALLY PURGE	50;1	SET	'1' FOR YES; '0' FOR NO; LAST EDITED: `JUL 19, 2005` DESCRIPTION: `This field is use to determine if the Extract Summary should be automatically purge after five years. This field will be check by the Reminder Extract code that runs monthly when running the National Extract.`
100	CLASS	100;1	SET	'N' FOR NATIONAL; 'V' FOR VISN; 'L' FOR LOCAL; LAST EDITED: `SEP 26, 2005` DESCRIPTION: `This is the CLASS of the extract summary. Possible classes are "N" for national, "V" for VISN, and "L" for local. National extract summaries cannot be edited by sites.`

Name	Field # of Occurrence
^%DT	.02+1, .03+1, .06+1
$$FMTE^DILIBF	ID.06+1

>>	Not killed explicitly
*	Changed
!	Killed
~	Newed

Name	Field # of Occurrence
>> %DT	.02+1, .03+1, .06+1*
>> DA	IXAVSL+1, IXAVKL+1, IXBSL+1, IXBKL+1, IXCSL+1, IXCKL+1, IXDSL+1, IXDKL+1
>> DA(1	IXAVSL+1, IXAVKL+1
U	ID.06+1
X	IXAVSL+1, IXAVKL+1, IXBSL+1, IXBKL+1, .001+1!, .01+1!, .02+1!, .03+1!, .04+1!, .06+1*! , .07+1!, .08+1!, 3+1!, 4+1!
X(1	IXCSL+1, IXCKL+1, IXDSL+1, IXDKL+1
X(2	IXCSL+1, IXCKL+1, IXDSL+1, IXDKL+1
X(3	IXDSL+1, IXDKL+1
>> Y	.02+1, .03+1, .06+1

Customize PDF page

Package: Clinical Reminders

Global: ^PXRMXT(810.3

Information

Description

Directly Accessed By Routines, Total: 31

Accessed By FileMan Db Calls, Total: 4

Pointer To FileMan Files, Total: 23

Fields, Total: 21

ICR, Total: 1

External References

Global Variables Directly Accessed

Naked Globals

Local Variables

Legend: