Home Package List Routine Alphabetical List Global Alphabetical List FileMan Files List FileMan Sub-Files List Package Component Lists Package-Namespace Mapping

Info | Desc | Pointed To By FileMan Files | Fields | Found Entries

Print Page as PDF

Global: ^MAGV(2006.914

Package: Imaging

Global: ^MAGV(2006.914

Information

FileMan FileNo	FileMan Filename	Package
2006.914	RETENTION POLICY	Imaging

Description

+---------------------------------------------------------------+ | | | Property of the US Government. | | No permission to copy or redistribute this software is given. | | Use of unreleased versions of this software requires the user | | to execute a written test agreement with the VistA Imaging | | Development Office of the Department of Veterans Affairs, | | telephone (301) 734-0100. | | | | The Food and Drug Administration classifies this software as | | a medical device. As such, it may not be changed in any way. | | Modifications to this software may result in an adulterated | | medical device under 21CFR820, the use of which is considered | | to be a violation of US Federal Statutes. | | | +---------------------------------------------------------------+ This file holds the various retention policies available to the storage subsystem. They come in two varieties: user-definable, and business. User-definable retention policies can be created and mapped to artifact descriptors, to serve as intrinsic retention policies. They can be inactivated, or "logically deleted", but only if no artifact descriptors are pointing to them. They can never be physically deleted, since there are artifacts that still point to the old retention policies, and we need to keep the historical record of retention policies that have been applied to this artifact over time. Business retention policies are designed to be called by business code for certain patients (e.g., Agent Orange retention policy, Employee retention policy, etc.). These retention policies will be installed with the patch and can be "replaced" with updated versions, but not deleted, since business logic will presumably expect to find them.

Pointed To By FileMan Files, Total: 3

Package	Total	FileMan Files
Imaging	3	ARTIFACT DESCRIPTOR(#2006.915)[.01] ARTIFACT RETENTION POLICY(#2006.921)[2] RETENTION POLICY STORAGE PROVIDER MAP(#2006.923)[.01]

Fields, Total: 7

Field #	Name	Loc	Type	Details
.01	DISPLAY NAME	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>64!($L(X)<1)!'(X'?1P.E) X` LAST EDITED: `MAR 08, 2010` HELP-PROMPT: `Answer must be 1-64 characters in length.` DESCRIPTION: `A text description of the policy for display by configuration user interface.` TECHNICAL DESCR: `Added in patch MAG3.034` CROSS-REFERENCE: `2006.914^B` `1)= S ^MAGV(2006.914,"B",$E(X,1,64),DA)=""` `2)= K ^MAGV(2006.914,"B",$E(X,1,64),DA)`
2	ARCHIVE DURATION YEARS	0;2	NUMBER	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `APR 08, 2010` HELP-PROMPT: `Type a Number between 0 and 999, 0 Decimal Digits.` DESCRIPTION: `The number of years from the duration trigger date that an artifact must be available.` TECHNICAL DESCR: `Added in patch MAG3.034`
3	ARCHIVE DURATION TRIGGER	0;3	SET	**********************REQUIRED FIELD********************** 'CD' FOR Create Date; 'LAD' FOR Last Accessed Date; 'DD' FOR Deceased Date; LAST EDITED: `MAR 12, 2010` HELP-PROMPT: `Enter Archive Duration Trigger.` DESCRIPTION: `The trigger event for initiating the countdown for archive duration.` TECHNICAL DESCR: `Added in patch MAG3.034`
4	MINIMUM ARCHIVE COPIES	0;4	NUMBER	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:+X'=X!(X>99)!(X<0)!(X?.E1"."1.N) X` LAST EDITED: `MAY 12, 2010` HELP-PROMPT: `Type a number between 0 and 99, 0 Decimal Digits.` DESCRIPTION: `Number of archive copies required by this retention policy.` TECHNICAL DESCR: `Added in patch MAG3.034`
5	MINIMUM OFFSITE COPIES	0;5	NUMBER	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:+X'=X!(X>99)!(X<0)!(X?.E1"."1.N) X` LAST EDITED: `MAY 12, 2010` HELP-PROMPT: `Type a number between 0 and 99, 0 Decimal Digits.` DESCRIPTION: `Number of offsite copies required by this retention policy.` TECHNICAL DESCR: `Added in patch MAG3.034`
6	BUSINESS KEY	0;6	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>64!($L(X)<1) X` LAST EDITED: `MAY 13, 2010` HELP-PROMPT: `Answer must be 1-64 characters in length.` DESCRIPTION: `Holds a key that can be used by clients to look up retention policies for specific business scenarios, e.g. Agent Orange cases, employees, etc.` `Business Key is not unique across all records, but must be unique among active records. In other words, you could have deactivated versions of old business keys (if already-captured artifacts are grandfathered in on the` `old policy), and a new, active record with the same key, so that newly acquired records follow the new policy.` TECHNICAL DESCR: `Added in patch MAG3.034` RECORD INDEXES: `BKEYACT (#1109)`
7	ACTIVE	0;7	SET	**********************REQUIRED FIELD********************** '0' FOR Inactive; '1' FOR Active; LAST EDITED: `AUG 04, 2011` HELP-PROMPT: `Select retention policy status.` DESCRIPTION: `Since many artifacts may be linked to a retention policy, it is not safe to delete records. However, the policy can be deactivated by setting this flag to false ("0"), so that it won't be assigned to newly acquired` `artifacts.` TECHNICAL DESCR: `Added in patch MAG3.034` RECORD INDEXES: `BKEYACT (#1109)`

Found Entries, Total: 1

DISPLAY NAME: Medical Information Retention Policy 75

Info | Desc | Pointed To By FileMan Files | Fields | Found Entries