| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | index | 0;1 | FREE TEXT | B | This property is the name on the index supported by the custodial package. Note: This is not the name of the cross reference being used internally. This is a easy to understand text that describes the content of the cross reference. For example: File: Patient Cross Reference: B Index: PATIENT NAME | |
| .02 | cross reference | 0;2 | FREE TEXT | This property indicates the specific internal VA FileMan cross reference associated with the index being defined. | ||
| .03 | type | 0;3 | SET OF CODES | 1:REGULAR 2:REGULAR DATE/TIME 3:COMPOSITE 4:COMPOSITE DATE/TIME | This property indicates the type of index being defined. Based on this type, various query object method will execute generic logic that applies to all indexes of the specified type. Note: Currently, 8/97, the 'COMPOSITE' type is not supported. Examples: Index Type ----- ---- ^SCE("C",DFN,DA) REGULAR ^SCE("B",DATETIME,DA) REGULAR DATE/TIME ^SCE("ADFN",DFN,DATETIME,DA) COMPOSITE DATE/TIME | |
| 101 | custom node validator | VALIDATOR;E1,245 | FREE TEXT | This property contains any query specific validator logic that the custodial pacakge needs performed. This logic is executed after the various methods execute the intrinic $QUERY function. Normally, the generic validator associated with the index type is sufficient and no custom logic is required. The validator checks to see if $QUERY returns a value that is beyond the scope of the query object's properties. For example, if your query is for a specific patient, the validator will check if a new patient has been reached by $QUERY. |
Error: Invalid Global File Type: 409.641