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

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Pointer To FileMan Files | Fields | All

Print Page as PDF

Global: ^ROR(799.2

Package: Clinical Case Registries

Global: ^ROR(799.2

Information

FileMan FileNo	FileMan Filename	Package
799.2	ROR METADATA	Clinical Case Registries

Description

THIS FILE MUST NOT BE MODIFIED LOCALLY! ONLY AUTHORIZED NATIONAL REGISTRY DEVELOPERS CAN EDIT THIS FILE! The ROR METADATA file contains descriptors of the files, data elements and APIs used by the registry update subsystem (search engine). These descriptors define relationships between files ("file-processing tree") used by the search engine, data elements and APIs. The expression parser uses data stored in this file to validate expressions that implement selection rules. Data from this file loaded and prepared by the $$METADATA^RORUPR1 function is used by the registry update process to load values of the data elements using appropriate APIs. Developers can use this file as a source of information required for definition of new selection rules for new national or local registries (supported files and data elements, APIs, DBIAs, etc.). All modifications of the registry update routines that affect the file-processing tree, APIs or supported data elements MUST be reflected in the ROR METADATA file. Records of this file have internal entry numbers equal to the corresponding file numbers.

Directly Accessed By Routines, Total: 5

Package	Total	Routines
Clinical Case Registries	5	ROR DATA ELEMENTS RORP018 RORSET01 RORUPEX RORUPR1

Accessed By FileMan Db Calls, Total: 3

Package	Total	Routines
Clinical Case Registries	3	RORP018 RORUPR1 RORUTL06

Pointed To By FileMan Files, Total: 1

Package	Total	FileMan Files
Clinical Case Registries	1	ROR METADATA(#799.2)[1]

Pointer To FileMan Files, Total: 1

Package	Total	FileMan Files
Clinical Case Registries	1	ROR METADATA(#799.2)[1]

Fields, Total: 5

Field #	Name	Loc	Type	Details
.01	FILE	0;1	NUMBER	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `Q:$$VAEDT^RORDD(799.2,,-1) K:+X'=X!(X>999999999999)!(X<2)!(X?.E1"."10.N) X I $D(X) K:'$$VFILE^DILFD(X) X S:$D(X) DINUM=X` LAST EDITED: `MAR 13, 2002` HELP-PROMPT: `Enter (sub)file number between 2 and 999999999999, 9 Decimal Digits.` DESCRIPTION: `The value of this field is the number of the (sub)file that can be searched for new data by the registry update process and is a part of the file-processing tree.` TECHNICAL DESCR: `The internal value of this field is used as the internal entry number of the record ('DINUM' feature).` DELETE TEST: `1,0)= I $$VADEL^RORDD(799.2,,-1)` `DELETE AUTHORITY: @` `WRITE AUTHORITY: @` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `799.2^B` `1)= S ^ROR(799.2,"B",$E(X,1,30),DA)=""` `2)= K ^ROR(799.2,"B",$E(X,1,30),DA)` `3)= Do not delete!`
1	PARENT	0;2	POINTER TO ROR METADATA FILE (#799.2)	ROR METADATA(#799.2) INPUT TRANSFORM: `Q:$$VAEDT^RORDD(799.2,,-1) S DIC("S")="I Y'="_+$G(DA) D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X` LAST EDITED: `MAR 13, 2002` DESCRIPTION: `This field holds the number of the (sub)file that is a parent of the current file in the file-processing tree. You can choose only from the files that have descriptors in the ROR METADATA file. However, the current record` `cannot be selected as the parent of itself.` `Leave this field empty for the "root" file (the PATIENT file (#2) most probably).` `See the technical description of the field for more information.` TECHNICAL DESCR: `During the registry update, VistA files are processed in the predetermined hierarchic sequence called "file-processing tree". A sample structure of the "tree" is illustrated below:` `. PATIENT (#2)` `. VISIT (#9000010)` `. V POV (#9000010.07)` `. PROBLEM (#9000011)` `. PTF (#45)` `. LAB DATA (#63)` `This means that for each patient a record in file #2 is processed first. Then patient visits from file #9000010 are processed. During processing of each visit record all linked "purpose of visit" records in file` `#9000010.07 are processed. After that, all patient records from the problem list are processed. Next in line are the patient records from file #45 and the lab results.` `The structure of the tree is defined by the routines that conduct the search (hard coded loops). However, it MUST be reflected in this file.` SCREEN: `S DIC("S")="I Y'="_+$G(DA)` EXPLANATION: `A record cannot be parent record of itself.` DELETE TEST: `1,0)= I $$VADEL^RORDD(799.2,,-1)` `DELETE AUTHORITY: @` `WRITE AUTHORITY: @` NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER`
2	DATA ELEMENT	2;0	Multiple #799.22	799.22 LAST EDITED: `MAR 26, 2002` DESCRIPTION: `This multiple stores a list of data elements supported by the search engine. These elements can be referenced by selection rules associated with the file.` `Records of the multiple are uniquely identified by the data element name (the primary key "B" and the uniqueness index "B" are used for this purpose).` `WRITE AUTHORITY: @` IDENTIFIED BY: `"WRITE": D EN^DDIOL(" "_$P(^(0),U,2),,"?35")` SECONDARY KEY: `A (#26)` `Uniqueness Index: DEC (#164) WHOLE FILE (#799.2)` `File, Field: 1) CODE (799.22,.02)` SECONDARY KEY: `B (#27)` `Uniqueness Index: B (#165)` `File, Field: 1) DATA NAME (799.22,.01)` INDEXED BY: `DATA NAME (B)`
3	API	3;0	Multiple #799.23	799.23 DESCRIPTION: `This multiple stores descriptors of the APIs that are used to load values of the search fields.` `Codes of the APIs are unique only in the file context. For example, the definition of any file can have a descriptor of the API #2.` `Internal entry numbers of the records in this multiple are equal to the codes of the APIs.` `WRITE AUTHORITY: @` IDENTIFIED BY: `"WRITE": D EN^DDIOL($P(^(0),U,3)_"^"_$P(^(0),U,2),,"?10")`
5	DESCRIPTION	5;0	WORD-PROCESSING #799.25	DESCRIPTION: `You can enter any additional reference information related to the file definition. The content of this field is not used by the application.` `WRITE AUTHORITY: @`

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Pointer To FileMan Files | Fields | All