TIU, listing signed notes titles in CPRS

86 views
Skip to first unread message

Ahmad Sharaf

unread,
Mar 8, 2011, 4:43:22 AM3/8/11
to Hardhats
Hi all,

our team found a bug in listing of the signed notes titles in CPRS,
for example and as you know after the physician signs a note the Title
of that note will contain extra piece of info separated by ";" of
that title which is the "STANDARD TITLE"

i.e.

NOTE TITLE;STANDARD TITLE,etc...

so as the physicians keep entering notes our team noticed that the
"STANDARD TITLE" does not match the one the "TIU DOCUMENT DEFINITION"
of that title.

i traced it down to the following routine :

header

TIUSRVLO ; SLC/JER - Server fns - lists for CPRS ;9/12/06 14:17
;;1.0;TEXT INTEGRATION
UTILITIES;**1,15,19,63,108,122,181,194,211**;Jun 20, 1997;Build 26

and i found it in "RESOLVE(DA) ; Resolve to external data" tag

Potential Bug in the following lines

I +$G(^TIU(8925.1,+DA,15)) D
. N TIUD15 S TIUD15=$G(^TIU(8925.1,+DA,15))

Notice that "DA" is the IEN of the NOTE as in "TIU DOCUMENT file
#8925" not the entry number of the Note definition as in "TIU DOCUMENT
DEFINITION 8925.1", so in that case it should be as the following

Proposed fix

I +$G(^TIU(8925.1,+TIUR0,15)) D
. N TIUD15 S TIUD15=$G(^TIU(8925.1,+TIUR0,15))

where "+TIUR0" is the entry number of note definition as in "TIU
DOCUMENT DEFINITION #8925.1" file

kdt...@gmail.com

unread,
Mar 8, 2011, 7:46:44 AM3/8/11
to Hardhats
I don't understand this.

In my listing in CPRS of signed notes (in the panel on the left hand
side of the screen in the notes tab), I see:

--<Date> <Note Title>, <Location>, <Author>
--<Date> <Note Title>, <Location>, <Author>
--<Date> <Note Title>, <Location>, <Author>
--<Date> <Note Title>, <Location>, <Author>
--<Date> <Note Title>, <Location>, <Author>

Can you clarify what erroneously shows up before this bug fix is
applied?

Thanks
Kevin

skip ormsby

unread,
Mar 8, 2011, 8:38:49 AM3/8/11
to hard...@googlegroups.com
Also, are you using MSC FileMan or VA FileMan?


a sharaf

unread,
Mar 9, 2011, 6:41:58 AM3/9/11
to hard...@googlegroups.com

in the following image (CPRS) notice the title separated by ";" the left side of it is the Title and the right part of it is the "standard title".

F1.JPG
to reproduce this case you have to configure the Tittle to have "VHA ENTERPRISE STANDARD TITLE" filled. as it shows in the screen shot of the terminal.    


F2.JPG


Skip im using "VA Fileman"
--
Sincerely,
Ahmad Sharaf.
F2.JPG
F1.JPG

skip ormsby

unread,
Mar 9, 2011, 8:04:08 AM3/9/11
to hard...@googlegroups.com
Ahmad, I "think" I see what is up.  Showing the TIU Document Def. was very helpful.  I looked at the VA FOIA for the same entry and saw:
NAME: ADVANCE DIRECTIVE                 ABBREVIATION: ADIR
  PRINT NAME: ADVANCE DIRECTIVE         TYPE: TITLE
  CLASS OWNER: CLINICAL COORDINATOR     STATUS: ACTIVE
  NATIONAL STANDARD: YES                OK TO DISTRIBUTE: YES
  TIMESTAMP: 57257,37175

Notice these fields are missing:
VHA ENTERPRISE STANDARD TITLE
MAP ATTEMPTED
MAP ATTEMPTED BY

Here is my suggestion for what it is worth:
1.  Put the code back to the original
2.  Delete the data in these fields for the ADVANCE DIRECTIVE entry:
VHA ENTERPRISE STANDARD TITLE
MAP ATTEMPTED
MAP ATTEMPTED BY
3.  Re-run to test.

If that fixes the problem we will go from there.
F1.JPG
F2.JPG

kdt...@gmail.com

unread,
Mar 9, 2011, 8:29:57 AM3/9/11
to Hardhats
Skip,

Look carefully at his code fix. I believe he is right. The unchanged
code pulls a pointer to file 8925, and then uses it in file 8925.1.

Kevin

On Mar 9, 8:04 am, skip ormsby <skip.orm...@gmail.com> wrote:
> Ahmad, I "think" I see what is up.  Showing the TIU Document Def. was very
> helpful.  I looked at the VA FOIA for the same entry and saw:
> NAME: ADVANCE DIRECTIVE                 ABBREVIATION: ADIR
>   PRINT NAME: ADVANCE DIRECTIVE         TYPE: TITLE
>   CLASS OWNER: CLINICAL COORDINATOR     STATUS: ACTIVE
>   NATIONAL STANDARD: YES                OK TO DISTRIBUTE: YES
>   TIMESTAMP: 57257,37175
>
> Notice these fields are missing:
> VHA ENTERPRISE STANDARD TITLE
> MAP ATTEMPTED
> MAP ATTEMPTED BY
>
> Here is my suggestion for what it is worth:
> 1.  Put the code back to the original
> 2.  Delete the data in these fields for the ADVANCE DIRECTIVE entry:
> VHA ENTERPRISE STANDARD TITLE
> MAP ATTEMPTED
> MAP ATTEMPTED BY
> 3.  Re-run to test.
>
> If that fixes the problem we will go from there.
>
>
>
> On Wed, Mar 9, 2011 at 6:41 AM, a sharaf <shara...@gmail.com> wrote:
>
> > in the following image (CPRS) notice the title separated by *";"* the left
> > side of it is the Title and the right part of it is the "standard title".
>
> > [image: F1.JPG]
> > to reproduce this case you have to configure the Tittle to have "VHA
> > ENTERPRISE STANDARD TITLE" filled. as it shows in the screen shot of the
> > terminal.
>
> > [image: F2.JPG]
>
> > Skip im using "VA Fileman"
>
>  F1.JPG
> 120KViewDownload
>
>  F2.JPG
> 64KViewDownload

skip ormsby

unread,
Mar 9, 2011, 8:40:48 AM3/9/11
to hard...@googlegroups.com
I did Kevin and then the question became - what is sitting on the 15th node?
^TIU(8925.1,D0,15)= (#1501) VHA ENTERPRISE STANDARD TITLE [1P:8926.1] ^
                 ==>(#1502) MAP ATTEMPTED [2D] ^ (#1503) MAP ATTEMPTED BY
                 ==>[3P:200] ^

those fields.  And as I said those fields are not populated in the VA FOIA.  Since your's works Kevin, does you entry have those fields populated?

skip ormsby

unread,
Mar 9, 2011, 8:51:46 AM3/9/11
to hard...@googlegroups.com
Or Kevin to put another way - your assuming that the data is correct and the code is wrong.  I on the other hand am looking at the VA example and that that the data is wrong and the code is right.

Ahmad Sharaf

unread,
Mar 9, 2011, 9:04:26 AM3/9/11
to Hardhats
skip

our team created new note titles to accommodate the hospital work
flow, but regardless of whether this field was populated or not, don't
you think that a bug in the code should be fixed.

skip ormsby

unread,
Mar 9, 2011, 9:29:12 AM3/9/11
to hard...@googlegroups.com
Ahmand it depends on what view you would like to take.  By altering the code instead of the data, you could (not saying you will) alter the built in business rules.  I have not done enough research to know why those fields are there and what they have to do with anything, maybe they are there for informational purposes.  What I do know and the only thing I do know is that those fields are not populated in the VA FOIA for that entry. It is really up to you all what view you want to take, just so long as it is well documented, which ever the direction.
I've got to go for now and fix my garage door so I can get my car out of it.

Patti Henderson

unread,
Mar 9, 2011, 10:01:06 AM3/9/11
to hard...@googlegroups.com

In spite of seeming totally ignorant here ---  is the purpose of this discussion to change the code so the title matches the Enterprise Standard title?  To remove the enterprise title   The difference between the two titles has a purpose ---can you explain why you think this is  a bug?

 

Patti Henderson

kdt...@gmail.com

unread,
Mar 9, 2011, 11:05:36 AM3/9/11
to Hardhats
When I look in my system, I don't see the error he describes. I don't
think I have data in those fields perhaps. But I looked at the code
and agreed that the pointer was being used incorrectly, so just
applied his fix.

Kevin

Sam Habiel

unread,
Mar 14, 2011, 10:03:35 AM3/14/11
to hard...@googlegroups.com
Skip,

I do have to address an assumption you are making: that the FOIA VISTA
serves as a reference. FOIA VISTA is unconfigured; and cannot serve as
a reference.

For example, you are not allowed to activate a new title without
mapping it to a VHA ENTERPRISE STANDARD TITLE. Therefore a VHA
Enterprise Standard Title is expected to exist for any new title
created by CACs.

-----
Select Action: Title// TITLE Title
Enter the Name of a new HISTORY AND PHYSICAL: TEST SAM TITLE

CLASS OWNER: CLINICAL COORDINATOR Replace

EVERY Local Title must be mapped to a VHA Enterprise Standard Title.


Direct Mapping to Enterprise Standard Title...
Your LOCAL Title is: TEST SAM TITLE

NOTE: Only ACTIVE Titles may be selected...

Select VHA ENTERPRISE STANDARD TITLE:

You didn't select a VHA Enterprise Standard Title...

... Try to map TEST SAM TITLE again? NO//


Recording the unmapped LOCAL Title: TEST SAM TITLE

STATUS: (A/I/T): INACTIVE// A ACTIVE

You MUST first map TEST SAM TITLE


Direct Mapping to Enterprise Standard Title...
Your LOCAL Title is: TEST SAM TITLE

NOTE: Only ACTIVE Titles may be selected...
---
But
---

GTM>W $$RESOLVE^TIUSRVLO(1790)

OUTPATIENT-PHYSICIAN;OPHTHALMOLOGY NOTE^3101227.1138^<elided patient
name> (�1214)^583;<elided provider name>;<elided provider name>^PHH
Gyne 2/<elided patient name>^completed^Visit: 12/27/10^
^^0^^^1^
---
The user asks: But this is a Gynecology note!!! (It really is; but we
don't have a separate note title for Gynecology).
---
From the TIU Document Definition file, we get the following:

OUTPUT FROM WHAT FILE: TIU DOCUMENT// TIU DOCUMENT DEFINITION (8925.1)
(946 entries)
Select TIU DOCUMENT DEFINITION NAME: OUTPATIENT-PHYSICIAN PHH-OUTPATIENT-PHYSIC
IAN TITLE
Std Title: PRIMARY CARE CLINICAL NOTE
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no Computed
Fields

NAME: PHH-OUTPATIENT-PHYSICIAN PRINT NAME: OUTPATIENT-PHYSICIAN


TYPE: TITLE CLASS OWNER: CLINICAL COORDINATOR

STATUS: ACTIVE SUPPRESS VISIT SELECTION: NO
VHA ENTERPRISE STANDARD TITLE: PRIMARY CARE CLINICAL NOTE
MAP ATTEMPTED: OCT 03, 2010@12:53:53 MAP ATTEMPTED BY: ALSHDIFAT,HANEEN
TIMESTAMP: 62002,46369

As we see, the Standard Title is "PRIMARY CARE CLINICAL NOTE", not
"OPHTHALMOLOGY NOTE", as $$RESOLVE outputs.

Sam

skip ormsby

unread,
Mar 14, 2011, 12:56:17 PM3/14/11
to hard...@googlegroups.com
Point well taken Sam, thanks.

Calvin Woolwine

unread,
Dec 20, 2014, 1:27:33 PM12/20/14
to hard...@googlegroups.com
We found this exact bug in our system and thanks to this discussion, we were able to correct this issue.  Thank you for the work you do.  It is appreciated.

Hartsel Bryant

unread,
Dec 20, 2014, 7:04:55 PM12/20/14
to hard...@googlegroups.com
Thank you all for posting the proposed fix for this issue.  We used it today to fix the same bug in our system (WorldVstA).  I work with Calvin Woolwine, who also thanked you in an earlier post.  Thanks to the WorldVistA team as well for walking us through applying this fix.

Hartsel E. Bryant,
Clinical Applications Specialist


On Tuesday, March 8, 2011 4:43:22 AM UTC-5, Ahmad Sharaf wrote:
Reply all
Reply to author
Forward
0 new messages