Visual Cross Reference Documentation Updated to include FileMan File pointer references

Detailed updates to Visual Cross Reference Documentation (http://code.osehra.org/dox_beta/index.html)

  • Documentation is generated based on FOIA release 12/06/2012.
  • Added a "File Man Files List" Page, this page lists all fileman files in VistA-FOIA sorted by fileman file number. Clicking any fileman file link in the list should bring a detailed page accociated with this fileman file, which consists of "Description", "Accessed By Routines" "Pointed to by FileMan Files", "Pointer to FileMan Files", and "Detailed Fields" and other information.
    • "Pointed to by FileMan Files" includes file pointers in sub-files. Each item in the table is formated as Link to FileMan File Name(#FileMan Number) followed by [], and inside the [] is a list of pointer field# or pointer field inside a sub-file seperated by comma. Clicking on the field# or #sub-file(field#) should bring you to the detail information about that pointer field. The same format applies to "Pointer to FileMan Files" as well.

    • "Fields" section listed all the fields defined in this FileMan File. If field is a multiple type, it provides a link to the sub-file detail page in the "Detail" column.

  • Updated Package dependencies to include fileman file pointer references. Again, the detailed information can be accessed by either clicking a link between  in direct graph or clicking the [#(R):#(G):#(F)] in the list table. If you mouse over a link in the direct graph, the tooltip also shows the detailed information about the dependencies between two packages.

  • "Globa Alphabetical List" Page now includes non-fileman file globals.

  • Categorized non-fileman file globals based on namespace, and updated the package dependencie.

  • Updated individual package page to include a Namespace section, also listed FileMan Files and Non-fileman file globals seperately.

  • A Preliminary Visual Cross Reference Documentaion based on WorldVistA DEWDrop Virtual Machine(http://www.fourthwatchsoftware.com/) is also available at (http://code.osehra.org/dox_alpha/worldvista/052912/index.html)
     

Big thanks to Peter Li for prodivding detailed instruction on how to get fileman file depencencies information and correcting a few problems in the review process, also WorldVistA to allow us to post the link in OSEHRA.

like0

Comments

Visual Cross Reference Documentation Updated to include FileMan

DAVID Whitten's picture

Trying again...

On Tue, Jun 12, 2012 at 5:25 PM, David Whitten <whitten@worldvista.org>wrote:

> On the Architecture call, this tool was demoed, and I wondered if you were
> marking Screened Pointers in any special way. Two types of fields in
> FileMan can have M code to filter out possible values, i.e. SET OF CODE and
> POINTER TO A FILE. The filtering code is defined in the variable DIC("S")
> as a result of Xecuting INPUT TRANSFORM of the field.
>
> I think there is a character stored in the 2nd piece of the
> ^DD(DDNUMBER,fieldnumber,0)
> that means there is a screen. Perhaps an '*" (STAR) character, ie:
> $CHAR(42) ?
> Note that if the extra character is not there, the DIC("S") will still be
> used, it just won't print on the screen. I think the character is to handle
> cases where a subroutine is called and the DIC("S") is not actually set in
> the INPUT TRANSFORM, but is SET when the subroutine is called.
>
> For example the NAME field of File #537025 has a screened pointer.
>
> Select DATA DICTIONARY UTILITY OPTION: LIST FILE ATTRIBUTES
> START WITH WHAT FILE: VAMC NETWORK HEALTH AUTHORIZED SITES//
> GO TO WHAT FILE: VAMC NETWORK HEALTH AUTHORIZED SITES//
> Select LISTING FORMAT: STANDARD//
> Start with field: FIRST// .01 NAME
> Go to field:
> DEVICE: 0;79;100 TELNET
> STANDARD DATA DICTIONARY
> #537025 -- VAMC NETWORK HEALTH AUTHORIZED SITES
> FILE JUN 12,2012@16:51:56
> PAGE 1
> STORED IN ^AFJ(537025, UCI:
> EHR,EHR (VERSION 5.1)
>
> DATA NAME GLOBAL DATA
> ELEMENT TITLE LOCATION TYPE
>
> ------------------------------------------------------------------------------
>
> 537025,.01 NAME 0;1 POINTER TO DOMAIN FILE (#4.2)
> (Required)
>
> INPUT TRANSFORM: S DIC("S")="I $P(^(0),U,2)'[""C""" D ^DIC
> K DIC S DIC=DIE,X=+Y K:Y<0 X
> LAST EDITED: NOV 15, 2001
> HELP-PROMPT: Enter the name of an authorized site.
> DESCRIPTION: Enter the name of the sites that you will
> send
> data requests to and receive data from.
> (Include your own site).
>
> SCREEN: S DIC("S")="I $P(^(0),U,2)'[""C"""
> EXPLANATION: You may not select closed domains.
> CROSS-REFERENCE: 537025^B
> 1)= S ^AFJ(537025,"B",$E(X,1,30),DA)=""
> 2)= K ^AFJ(537025,"B",$E(X,1,30),DA)
>
>
> Another example (which doesn't have the "*" character)
> would be the ORDERABLE ITEM multiple in the UNIT DOSE ORDER SET file:
>
> Select DATA DICTIONARY UTILITY OPTION: LIST FILE ATTRIBUTES
> START WITH WHAT FILE: UNIT DOSE ORDER SET//
> GO TO WHAT FILE: UNIT DOSE ORDER SET//
> Select SUB-FILE: ORDERABLE ITEM
> Select SUB-FILE:
> Select LISTING FORMAT: STANDARD//
> Start with field: FIRST// .01 ORDERABLE ITEM
> Go to field:
> DEVICE: TELNET
> STANDARD DATA DICTIONARY #53.22 -- ORDERABLE ITEM SUB-FILE
> JUN 12,2012@17:19:42
> PAGE 1
> STORED IN ^PS(53.2,D0,2, UCI: EHR,EHR
>
> DATA NAME GLOBAL DATA
> ELEMENT TITLE LOCATION TYPE
>
> -------------------------------------------------------------------------------
>
> 53.22,.01 ORDERABLE ITEM 0;1 POINTER TO PHARMACY ORDERABLE
> ITEM FIL
> E (#50.7) (Multiply asked)
>
> INPUT TRANSFORM: S DIC("S")="I
> $S('$P($G(^(0)),U,4):1,1:$P($G(^(
> 0)),U,4)>DT)"
> LAST EDITED: DEC 11, 1997
> HELP-PROMPT: Enter the orderable item to identify this
> medication. Each orderable item chosen is
> an
> individual order within the order set.
> DESCRIPTION: This is the orderable item for the
> medication
> order.
>
> GROUP: PSJU
> NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
>
> CROSS-REFERENCE: 53.22^B
> 1)= S
> ^PS(53.2,DA(1),2,"B",$E(X,1,30),DA)=""
> 2)= K ^PS(53.2,DA(1),2,"B",$E(X,1,30),DA)
>
>
>
>
>
> On Thu, May 31, 2012 at 5:14 PM, jason.li <jason.li@kitware.com> wrote:
>
>> Detailed updates to Visual Cross Reference Documentation (
>> http://code.osehra.org/dox_beta/index.html)
>>
>> - Documentation is generated based on FOIA release 12/06/2012.
>> - Added a "File Man Files List" Page, this page lists all fileman
>> files in VistA-FOIA sorted by fileman file number. Clicking any fileman
>> file link in the list should bring a detailed page accociated with this
>> fileman file, which consists of "Description", "Accessed By Routines"
>> "Pointed to by FileMan Files", "Pointer to FileMan Files", and "Detailed
>> Fields" and other information.
>> -
>>
>> "Pointed to by FileMan Files" includes file pointers in sub-files.
>> Each item in the table is formated as Link to FileMan File Name(#FileMan
>> Number) followed by [], and inside the [] is a list of pointer field# or
>> pointer field inside a sub-file seperated by comma. Clicking on the field#
>> or #sub-file(field#) should bring you to the detail information about that
>> pointer field. The same format applies to "Pointer to FileMan Files" as
>> well.
>> -
>>
>> "Fields" section listed all the fields defined in this FileMan
>> File. If field is a multiple type, it provides a link to the sub-file
>> detail page in the "Detail" column.
>> -
>>
>> Updated Package dependencies to include fileman file pointer
>> references. Again, the detailed information can be accessed by either
>> clicking a link between in direct graph or clicking the [#(R):#(G):#(F)]
>> in the list table. If you mouse over a link in the direct graph, the
>> tooltip also shows the detailed information about the dependencies between
>> two packages.
>> -
>>
>> "Globa Alphabetical List" Page now includes non-fileman file globals.
>> -
>>
>> Categorized non-fileman file globals based on namespace, and updated
>> the package dependencie.
>> -
>>
>> Updated individual package page to include a Namespace section, also
>> listed FileMan Files and Non-fileman file globals seperately.
>> -
>>
>> A Preliminary Visual Cross Reference Documentaion based on WorldVistA
>> DEWDrop Virtual Machine(http://www.fourthwatchsoftware.com/) is also
>> available at (
>> http://code.osehra.org/dox_alpha/worldvista/052912/index.html)
>>
>>
>> Big thanks to Peter Li for prodivding detailed instruction on how to get
>> fileman file depencencies information and correcting a few problems in the
>> review process, also WorldVistA to allow us to post the link in OSEHRA.
>>
>> Promote content
>> Group sticky:
>>
>> Not Sticky
>>
>> Featured content:
>>
>> Not Featured
>> --
>> Full post:
>> http://www.osehra.org/blog/visual-cross-reference-documentation-updated-...
>> Manage my subscriptions:
>> http://www.osehra.org/og_mailinglist/subscriptions
>> Stop emails for this post:
>> http://www.osehra.org/og_mailinglist/unsubscribe/759
>>
>
>

like0

Visual Cross Reference Documentation Updated to include FileMan

Peter Li's picture

Hi David,

Thanks for the pointer. No, we have not looked at the M code associated
with the screened pointer. I know there are M code buried in many nooks in
the data dictionary - input transform, cross reference, options, template,
protocol, rpc. We'll tried to bring them out one by one.

Please do let us know when we miss something. Again, our goal is to make
the tool as useful as possible for future development.

Peter

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of David Whitten
Sent: Tuesday, June 12, 2012 5:43 PM
To: development-tools@groups.osehra.org
Subject: Re: [development-tools] Visual Cross Reference Documentation
Updated to include FileMan File pointer references

Trying again...

On Tue, Jun 12, 2012 at 5:25 PM, David Whitten <whitten@worldvista.org>
wrote:

On the Architecture call, this tool was demoed, and I wondered if you were
marking Screened Pointers in any special way. Two types of fields in
FileMan can have M code to filter out possible values, i.e. SET OF CODE and
POINTER TO A FILE. The filtering code is defined in the variable DIC("S")
as a result of Xecuting INPUT TRANSFORM of the field.

I think there is a character stored in the 2nd piece of the
^DD(DDNUMBER,fieldnumber,0)
that means there is a screen. Perhaps an '*" (STAR) character, ie:
$CHAR(42) ?
Note that if the extra character is not there, the DIC("S") will still be
used, it just won't print on the screen. I think the character is to handle
cases where a subroutine is called and the DIC("S") is not actually set in
the INPUT TRANSFORM, but is SET when the subroutine is called.

For example the NAME field of File #537025 has a screened pointer.

Select DATA DICTIONARY UTILITY OPTION: LIST FILE ATTRIBUTES
START WITH WHAT FILE: VAMC NETWORK HEALTH AUTHORIZED SITES//
GO TO WHAT FILE: VAMC NETWORK HEALTH AUTHORIZED SITES//
Select LISTING FORMAT: STANDARD//
Start with field: FIRST// .01 NAME
Go to field:
DEVICE: 0;79;100 TELNET
STANDARD DATA DICTIONARY
#537025 -- VAMC NETWORK HEALTH AUTHORIZED SITES FILE
JUN 12,2012@16:51:56 PAGE 1
STORED IN ^AFJ(537025, UCI: EHR,EHR
(VERSION 5.1)

DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
----------------------------------------------------------------------------
--

537025,.01 NAME 0;1 POINTER TO DOMAIN FILE (#4.2)
(Required)

INPUT TRANSFORM: S DIC("S")="I $P(^(0),U,2)'[""C""" D ^DIC K
DIC S DIC=DIE,X=+Y K:Y<0 X
LAST EDITED: NOV 15, 2001
HELP-PROMPT: Enter the name of an authorized site.
DESCRIPTION: Enter the name of the sites that you will
send
data requests to and receive data from.
(Include your own site).

SCREEN: S DIC("S")="I $P(^(0),U,2)'[""C"""
EXPLANATION: You may not select closed domains.
CROSS-REFERENCE: 537025^B
1)= S ^AFJ(537025,"B",$E(X,1,30),DA)=""
2)= K ^AFJ(537025,"B",$E(X,1,30),DA)

Another example (which doesn't have the "*" character)
would be the ORDERABLE ITEM multiple in the UNIT DOSE ORDER SET file:

Select DATA DICTIONARY UTILITY OPTION: LIST FILE ATTRIBUTES
START WITH WHAT FILE: UNIT DOSE ORDER SET//
GO TO WHAT FILE: UNIT DOSE ORDER SET//
Select SUB-FILE: ORDERABLE ITEM
Select SUB-FILE:
Select LISTING FORMAT: STANDARD//
Start with field: FIRST// .01 ORDERABLE ITEM
Go to field:
DEVICE: TELNET
STANDARD DATA DICTIONARY #53.22 -- ORDERABLE ITEM SUB-FILE
JUN 12,2012@17:19:42
PAGE 1
STORED IN ^PS(53.2,D0,2, UCI: EHR,EHR

DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
----------------------------------------------------------------------------
---

53.22,.01 ORDERABLE ITEM 0;1 POINTER TO PHARMACY ORDERABLE ITEM
FIL
E (#50.7) (Multiply asked)

INPUT TRANSFORM: S DIC("S")="I
$S('$P($G(^(0)),U,4):1,1:$P($G(^(
0)),U,4)>DT)"
LAST EDITED: DEC 11, 1997
HELP-PROMPT: Enter the orderable item to identify this
medication. Each orderable item chosen is an
individual order within the order set.
DESCRIPTION: This is the orderable item for the
medication
order.

GROUP: PSJU
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

CROSS-REFERENCE: 53.22^B
1)= S ^PS(53.2,DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^PS(53.2,DA(1),2,"B",$E(X,1,30),DA)

On Thu, May 31, 2012 at 5:14 PM, jason.li <jason.li@kitware.com> wrote:

Detailed updates to Visual Cross Reference Documentation
(http://code.osehra.org/dox_beta/index.html)

* Documentation is generated based on FOIA release 12/06/2012.
* Added a "File Man Files List" Page, this page lists all fileman
files in VistA-FOIA sorted by fileman file number. Clicking any fileman file
link in the list should bring a detailed page accociated with this fileman
file, which consists of "Description", "Accessed By Routines" "Pointed to by
FileMan Files", "Pointer to FileMan Files", and "Detailed Fields" and other
information.

o "Pointed to by FileMan Files" includes file pointers in sub-files. Each
item in the table is formated as Link to FileMan File Name(#FileMan Number)
followed by [], and inside the [] is a list of pointer field# or pointer
field inside a sub-file seperated by comma. Clicking on the field# or
#sub-file(field#) should bring you to the detail information about that
pointer field. The same format applies to "Pointer to FileMan Files" as
well.

o "Fields" section listed all the fields defined in this FileMan File. If
field is a multiple type, it provides a link to the sub-file detail page in
the "Detail" column.

. Updated Package dependencies to include fileman file pointer
references. Again, the detailed information can be accessed by either
clicking a link between in direct graph or clicking the [#(R):#(G):#(F)] in
the list table. If you mouse over a link in the direct graph, the tooltip
also shows the detailed information about the dependencies between two
packages.

. "Globa Alphabetical List" Page now includes non-fileman file
globals.

. Categorized non-fileman file globals based on namespace, and
updated the package dependencie.

. Updated individual package page to include a Namespace section,
also listed FileMan Files and Non-fileman file globals seperately.

. A Preliminary Visual Cross Reference Documentaion based on
WorldVistA DEWDrop Virtual Machine(http://www.fourthwatchsoftware.com/) is
also available at
(http://code.osehra.org/dox_alpha/worldvista/052912/index.html)

Big thanks to Peter Li for prodivding detailed instruction on how to get
fileman file depencencies information and correcting a few problems in the
review process, also WorldVistA to allow us to post the link in OSEHRA.

Promote content
Group sticky:

Not Sticky

Featured content:

Not Featured

--
Full post:
http://www.osehra.org/blog/visual-cross-reference-documentation-updated-...
<http://www.osehra.org/blog/visual-cross-reference-documentation-updated-inc
lude-fileman-file-pointer-references>
Manage my subscriptions: http://www.osehra.org/og_mailinglist/subscriptions
Stop emails for this post:
http://www.osehra.org/og_mailinglist/unsubscribe/759

like0

wiki and screens

Christopher Edwards's picture

Peter & Jason:

I have started a wiki with the relevant portions of understanding the Data Dictionary here:  http://wiki.osehra.org/display/VAF/Data+Dictionary.

accoding to the programmer manual:

^DD(filenumber,fieldnumber,0) Field Definition 0 node
 Piece 1 = Field label
 Piece 2 = Field attributes (can have multiple) - definitions Page 479 fm22_0pm.pdf (they are also below this line in the wiki)

*If there is a screen associated with a pointer or set of codes data type.

^DD(filenumber,fieldnumber,12.1) Contains the code which sets DIC("S") if a screen has been written for a pointer or a set of codes.

David:  does this capture the locations of data in your comment?

like0

Visual Cross Reference Documentation Updated to include FileMan

Jason Li's picture

Hi David,

Thanks again for detailed information on how to handle screened pointers,
just as Peter pointed out, right now we do not distinguish them among other
file pointers. Our next step is just to display the detailed information as
generated by Data Dictionary Utilities option 1: List File Attributes for
each fields, should be identical to the result you just posted for those
two types of screened pointers. Once that is down we will be focusing on
how to extract dependencies based on M[umps] code stored in the schema.
Right now I do not have a nice way to handle those other than fake a
routine based on the code and feed to XINDEX for results, it would be
appreciated if you have any suggestions.

Thanks,
- Jason

On Tue, Jun 12, 2012 at 9:51 PM, pli <pli@tiag.net>

> Hi David,****
>
> ** **
>
> Thanks for the pointer. No, we have not looked at the M code associated
> with the screened pointer. I know there are M code buried in many nooks in
> the data dictionary – input transform, cross reference, options, template,
> protocol, rpc. We’ll tried to bring them out one by one.****
>
> ** **
>
> Please do let us know when we miss something. Again, our goal is to make
> the tool as useful as possible for future development.****
>
> ** **
>
> Peter****
>
> ** **
>
> ****
>
> ** **
>
> *From:* Apache [mailto:apache@groups.osehra.org] *On Behalf Of *David
> Whitten
> *Sent:* Tuesday, June 12, 2012 5:43 PM
> *To:* development-tools@groups.osehra.org
>
> *Subject:* Re: [development-tools] Visual Cross Reference Documentation
> Updated to include FileMan File pointer references****
>
> ** **
>
> Trying again...****
>
> On Tue, Jun 12, 2012 at 5:25 PM, David Whitten <whitten@worldvista.org>
> wrote:****
>
> On the Architecture call, this tool was demoed, and I wondered if you were
> marking Screened Pointers in any special way. Two types of fields in
> FileMan can have M code to filter out possible values, i.e. SET OF CODE and
> POINTER TO A FILE. The filtering code is defined in the variable DIC("S")
> as a result of Xecuting INPUT TRANSFORM of the field.
>
> I think there is a character stored in the 2nd piece of the
> ^DD(DDNUMBER,fieldnumber,0)
> that means there is a screen. Perhaps an '*" (STAR) character, ie:
> $CHAR(42) ?
> Note that if the extra character is not there, the DIC("S") will still be
> used, it just won't print on the screen. I think the character is to handle
> cases where a subroutine is called and the DIC("S") is not actually set in
> the INPUT TRANSFORM, but is SET when the subroutine is called.
>
> For example the NAME field of File #537025 has a screened pointer.
>
> Select DATA DICTIONARY UTILITY OPTION: LIST FILE ATTRIBUTES
> START WITH WHAT FILE: VAMC NETWORK HEALTH AUTHORIZED SITES//
> GO TO WHAT FILE: VAMC NETWORK HEALTH AUTHORIZED SITES//
> Select LISTING FORMAT: STANDARD//
> Start with field: FIRST// .01 NAME
> Go to field:
> DEVICE: 0;79;100 TELNET
> STANDARD DATA DICTIONARY
> #537025 -- VAMC NETWORK HEALTH AUTHORIZED SITES
> FILE JUN 12,2012@16:51:56
> PAGE 1
> STORED IN ^AFJ(537025, UCI:
> EHR,EHR (VERSION 5.1)
>
> DATA NAME GLOBAL DATA
> ELEMENT TITLE LOCATION TYPE
>
> ------------------------------------------------------------------------------
>
> 537025,.01 NAME 0;1 POINTER TO DOMAIN FILE (#4.2)
> (Required)
>
> INPUT TRANSFORM: S DIC("S")="I $P(^(0),U,2)'[""C""" D ^DIC
> K DIC S DIC=DIE,X=+Y K:Y<0 X
> LAST EDITED: NOV 15, 2001
> HELP-PROMPT: Enter the name of an authorized site.
> DESCRIPTION: Enter the name of the sites that you will
> send
> data requests to and receive data from.
> (Include your own site).
>
> SCREEN: S DIC("S")="I $P(^(0),U,2)'[""C"""
> EXPLANATION: You may not select closed domains.
> CROSS-REFERENCE: 537025^B
> 1)= S ^AFJ(537025,"B",$E(X,1,30),DA)=""
> 2)= K ^AFJ(537025,"B",$E(X,1,30),DA)
>
>
> Another example (which doesn't have the "*" character)
> would be the ORDERABLE ITEM multiple in the UNIT DOSE ORDER SET file:
>
> Select DATA DICTIONARY UTILITY OPTION: LIST FILE ATTRIBUTES
> START WITH WHAT FILE: UNIT DOSE ORDER SET//
> GO TO WHAT FILE: UNIT DOSE ORDER SET//
> Select SUB-FILE: ORDERABLE ITEM
> Select SUB-FILE:
> Select LISTING FORMAT: STANDARD//
> Start with field: FIRST// .01 ORDERABLE ITEM
> Go to field:
> DEVICE: TELNET
> STANDARD DATA DICTIONARY #53.22 -- ORDERABLE ITEM SUB-FILE
> JUN 12,2012@17:19:42
> PAGE 1
> STORED IN ^PS(53.2,D0,2, UCI: EHR,EHR
>
> DATA NAME GLOBAL DATA
> ELEMENT TITLE LOCATION TYPE
>
> -------------------------------------------------------------------------------
>
> 53.22,.01 ORDERABLE ITEM 0;1 POINTER TO PHARMACY ORDERABLE
> ITEM FIL
> E (#50.7) (Multiply asked)
>
> INPUT TRANSFORM: S DIC("S")="I
> $S('$P($G(^(0)),U,4):1,1:$P($G(^(
> 0)),U,4)>DT)"
> LAST EDITED: DEC 11, 1997
> HELP-PROMPT: Enter the orderable item to identify this
> medication. Each orderable item chosen is
> an
> individual order within the order set.
> DESCRIPTION: This is the orderable item for the
> medication
> order.
>
> GROUP: PSJU
> NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
>
> CROSS-REFERENCE: 53.22^B
> 1)= S
> ^PS(53.2,DA(1),2,"B",$E(X,1,30),DA)=""
> 2)= K ^PS(53.2,DA(1),2,"B",$E(X,1,30),DA)*
> ***
>
>
>
>
>
> ****
>
> On Thu, May 31, 2012 at 5:14 PM, jason.li <jason.li@kitware.com> wrote:***
> *
>
> Detailed updates to Visual Cross Reference Documentation (
> http://code.osehra.org/dox_beta/index.html)****
>
> - Documentation is generated based on FOIA release 12/06/2012.****
> - Added a "File Man Files List" Page, this page lists all fileman
> files in VistA-FOIA sorted by fileman file number. Clicking any fileman
> file link in the list should bring a detailed page accociated with this
> fileman file, which consists of "Description", "Accessed By Routines"
> "Pointed to by FileMan Files", "Pointer to FileMan Files", and "Detailed
> Fields" and other information. ****
>
> **o **"Pointed to by FileMan Files" includes file pointers in
> sub-files. Each item in the table is formated as Link to FileMan File
> Name(#FileMan Number) followed by [], and inside the [] is a list of
> pointer field# or pointer field inside a sub-file seperated by comma.
> Clicking on the field# or #sub-file(field#) should bring you to the detail
> information about that pointer field. The same format applies to "Pointer
> to FileMan Files" as well.****
>
> **o **"Fields" section listed all the fields defined in this FileMan
> File. If field is a multiple type, it provides a link to the sub-file
> detail page in the "Detail" column.****
>
> **· **Updated Package dependencies to include fileman file
> pointer references. Again, the detailed information can be accessed by
> either clicking a link between in direct graph or clicking the
> [#(R):#(G):#(F)] in the list table. If you mouse over a link in the direct
> graph, the tooltip also shows the detailed information about the
> dependencies between two packages.****
>
> **· **"Globa Alphabetical List" Page now includes non-fileman
> file globals.****
>
> **· **Categorized non-fileman file globals based on namespace,
> and updated the package dependencie.****
>
> **· **Updated individual package page to include a Namespace
> section, also listed FileMan Files and Non-fileman file globals seperately.
> ****
>
> **· **A Preliminary Visual Cross Reference Documentaion based on
> WorldVistA DEWDrop Virtual Machine(http://www.fourthwatchsoftware.com/)
> is also available at (
> http://code.osehra.org/dox_alpha/worldvista/052912/index.html)
> ****
>
> Big thanks to Peter Li for prodivding detailed instruction on how to get
> fileman file depencencies information and correcting a few problems in the
> review process, also WorldVistA to allow us to post the link in OSEHRA.***
> *
>
> Promote content
> Group sticky: ****
>
> Not Sticky ****
>
> Featured content: ****
>
> Not Featured ****
>
> --
> Full post:
> http://www.osehra.org/blog/visual-cross-reference-documentation-updated-...
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/759****
>
> ** **
>
> ** **
>

--
Jason Li
Kitware, Inc.
R&D Engineer
28 Corporate Dr
Clifton Park, NY 12065

like0

Visual Cross Reference Documentation Updated to include FileMan

Jason Li's picture

More updates:

http://code.osehra.org/dox/index.html<http://code.osehra.org/dox_beta/in...
is
now the same as http://code.osehra.org/dox_beta/index.html, they both are
based on FOIA release 12/06/2011.

Please use the following link to access FOIA release 08/19/2011.

http://code.osehra.org/dox/081911/index.html

Again, documentation for FOIA release 08/19/2011 is also regenerated
with latest update.

As links to globals have been changed, you might have to clear Web browser
cache and try again.

Source code to generate the documentation is also pushed for review. (
http://review.code.osehra.org/#/c/182/)

On Thu, May 31, 2012 at 5:14 PM, jason.li <jason.li@kitware.com> wrote:

> Detailed updates to Visual Cross Reference Documentation (
> http://code.osehra.org/dox_beta/index.html)
>
> - Documentation is generated based on FOIA release 12/06/2012.
> - Added a "File Man Files List" Page, this page lists all fileman
> files in VistA-FOIA sorted by fileman file number. Clicking any fileman
> file link in the list should bring a detailed page accociated with this
> fileman file, which consists of "Description", "Accessed By Routines"
> "Pointed to by FileMan Files", "Pointer to FileMan Files", and "Detailed
> Fields" and other information.
> -
>
> "Pointed to by FileMan Files" includes file pointers in sub-files.
> Each item in the table is formated as Link to FileMan File Name(#FileMan
> Number) followed by [], and inside the [] is a list of pointer field# or
> pointer field inside a sub-file seperated by comma. Clicking on the field#
> or #sub-file(field#) should bring you to the detail information about that
> pointer field. The same format applies to "Pointer to FileMan Files" as
> well.
> -
>
> "Fields" section listed all the fields defined in this FileMan
> File. If field is a multiple type, it provides a link to the sub-file
> detail page in the "Detail" column.
> -
>
> Updated Package dependencies to include fileman file pointer
> references. Again, the detailed information can be accessed by either
> clicking a link between in direct graph or clicking the [#(R):#(G):#(F)]
> in the list table. If you mouse over a link in the direct graph, the
> tooltip also shows the detailed information about the dependencies between
> two packages.
> -
>
> "Globa Alphabetical List" Page now includes non-fileman file globals.
> -
>
> Categorized non-fileman file globals based on namespace, and updated
> the package dependencie.
> -
>
> Updated individual package page to include a Namespace section, also
> listed FileMan Files and Non-fileman file globals seperately.
> -
>
> A Preliminary Visual Cross Reference Documentaion based on WorldVistA
> DEWDrop Virtual Machine(http://www.fourthwatchsoftware.com/) is also
> available at (
> http://code.osehra.org/dox_alpha/worldvista/052912/index.html)
>
>
> Big thanks to Peter Li for prodivding detailed instruction on how to get
> fileman file depencencies information and correcting a few problems in the
> review process, also WorldVistA to allow us to post the link in OSEHRA.
>
> Promote content
> Group sticky:
>
> Not Sticky
>
> Featured content:
>
> Not Featured
> --
> Full post:
> http://www.osehra.org/blog/visual-cross-reference-documentation-updated-...
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/759
>

--
Jason Li
Kitware, Inc.
R&D Engineer
28 Corporate Dr
Clifton Park, NY 12065

like0