﻿__group__	ticket	summary	component	version	milestone	type	owner	status	created	_changetime	_description	_reporter
Active Tickets	19	how to find source code	CPRS			task	Kevin Toppenberg	new	2010-11-15T01:23:54-05:00	2010-11-15T01:23:54-05:00	"I have downloaded astronaut-windows-vm-beta-0.7.3-complete.exe. From where can I find the source code of this?

Thanks"	thari
Active Tickets	10	Bug in the Fileman import data code (DDMP)...	WorldVistA EHR			defect		new	2009-12-24T10:24:17-05:00	2009-12-24T10:24:17-05:00	"Here's the situation:

I am trying to import a (rather large) drug file into Vista from a
csv. Every single time I import, however, the fields seem to get
scrambled so that data don't file because the wrong data types get
filed into fields. For example (file name edited, file isn't called
""Drugs"").

Record #1 Rejected:
  The value 'No DEA Class Code assigned' for field MED ROUTE ID in
file DRUGS is not valid.
Record #2 Rejected:
  The value '41101' for field MED REF GEN DRUG NAME CD in file DRUGS
is not valid.
Record #3 Rejected:
  The value '00281024' for field MED REF GEN DRUG NAME CD in file
DRUGS is not valid.

Using the GT.M native debugger, and then Serenji, I was able to
pinpoint down the problem:
In PARSE+15^DDMP, there is this line:

S DDMPIN=$P(DDMPIN,DDMPTVAL,2)

The intent of this line is to chop DDMPTVAL from the beginning of
DDMPIN. It works almost all of the time, with one exception: when
DDMPTVAL occurs twice in succession.

GTM> w DDMPIN
""Erythromycin (Bulk) Powder"",""Erythromycin (Bulk)
Powder"",""0"",00035,00077827,00093978,"""","""",""Misc"",""Misc.(Non-Drug;
Combo Route)"",""Powd"",""Powder"","""",""Powder

GTM> w DDMPTVAL
""Erythromycin (Bulk) Powder""

GTM> W $P(DDMPIN,DDMPTVAL,2)
,
(instead of the expected ,""Erythromycin (Bulk)
Powder"",""0"",00035,00077827,00093978,"""","""",""Misc"",""Misc.(Non-Drug;
Combo Route)"",""Powd"",""Powder"","""",""Powder)

That's why my fields were getting scrambled. The routine thinks that
my csv input has ended and moves on to the next part.

Sam
PS: I am using the latest and greatest MSC FileMan 22.1036

Bugfix:
Change the above mentioned line to this:
... S DDMPIN=$E(DDMPIN,$L(DDMPTVAL)+1,$L(DDMPIN))

I verified that it works with the import that crashed."	Sam Habiel
Active Tickets	12	"%DT flag ""I""  (for international input) prevent Fileman from accepting month names in Dates. CPRS relies on that."	WorldVistA EHR			defect		new	2010-01-31T08:50:14-05:00	2010-01-31T08:50:14-05:00	"http://groups.google.com/group/hardhats/browse_thread/thread/837ea0d05a749bc0
"	Sam Habiel
Active Tickets	20	Make NPI optional	CCD-CCR			defect	George Lilly	new	2012-05-21T09:47:40-04:00	2012-05-21T09:47:40-04:00	"The National Provider Identifier code doesn't work in plain vanilla OpenVista.  Can we make it optional?  $$NPI^XUSNPI is called in C0CVA200, which is in some later distribution.

Could we either allow an option in the options file that excludes NPI lookup?
"	Mike Cham
Active Tickets	21	Setup RPC functions during KID Install	CCD-CCR			enhancement	George Lilly	new	2012-05-21T09:49:58-04:00	2012-05-21T09:49:58-04:00	"Does it make sense to automatically add the relevant CCR/CCD functions to the rpc file?  And then add them to the OR CPRS GUI CHART context?
"	Mike Cham
Active Tickets	22	Expand CCD data	CCD-CCR	2.0		enhancement	sanchu	assigned	2012-05-21T09:55:18-04:00	2012-05-25T13:58:28-04:00	"The CCD code only includes vitals and problems.  Can we get it to include the other relevant data elements?
"	Mike Cham
Active Tickets	14	Issue in listing down the Radiology order status in reports tab in CPRS	CPRS			defect	Kevin Toppenberg	new	2010-04-08T07:43:36-04:00	2010-04-08T07:43:36-04:00	"We faced an issue on Status list for radiology orders on Reports tab. 


Replication Steps: 


1. Make more than 4 radiology orders 
2. Select all the four and sign at once 
3. Go to Reports tab 
4. Select Clinical reports -- Radiology 
5. and click on Status menu 
6. you could see only one or two items listed but not all. 


Reason for the issue: ( if at all it is not supposed to be VistA 
functionality) 


Since all new orders signed at same time, some global entries taken 
the same date time. 


for example ,, 


^TMP(""GMTSRAD"",7488,6899590.898492,3,847)=""3100408.101508^p^ABDOMEN 
LATERAL VIEW|(ONE FILM)^^MANAGER,SYSTEM"" 
^TMP(""GMTSRAD"",7488,6899590.898492,3,847,0)="""" 
^TMP(""GMTSRAD"",7488,6899590.898492,4,846)=""3100408.101508^p^ABDOMEN 
FOR PREGNANCY^^MANAGER,SYSTEM"" 
^TMP(""GMTSRAD"",7488,6899590.898492,4,846,0)="""" 
^TMP(""GMTSRAD"",7488,6899590.898492,5,848)=""3100408.101508^p^BARIUM 
MEAL COMPLETE^^MANAGER,SYSTEM"" 
^TMP(""GMTSRAD"",7488,6899590.898492,5,848,0)="""" 
^TMP(""GMTSRAD"",7488,6899590.898494,2,627)=""3100408.101506^p^ABDOMEN AP OR ERECT (ONE|FILM)^^MANAGER,SYSTEM"" 
^TMP(""GMTSRAD"",7488,6899590.898494,2,627,0)="""" 


but the OE/RR reports ^TMP(""ORDATA"", nodes is gettting overwritten by the nodes having the same dates. please check the code pasted under solution.


Solution: 


In RS^ORDV03, 


...S CNT=CNT+1 
 ...S SITE=$S($L($G(^TMP(""GMTSRAD"", 
$J,ORDT,ORDA,ORDA2,""facility""))):^(""facility""),1:ORSITE) 
 ...;[ELN] 
 ...;S ^TMP(""ORDATA"",$J,ORDT,""WP"",1)=""1^""_SITE 
 ...S ^TMP(""ORDATA"",$J,ORDA,""WP"",1)=""1^""_SITE 
 ...;S ^TMP(""ORDATA"",$J,ORDT,""WP"",2)=""2^""_$$DATE^ORDVU($P(REC,""^"")) 
 ...S ^TMP(""ORDATA"",$J,ORDA,""WP"",2)=""2^""_$$DATE^ORDVU($P(REC,""^"")) 
 ...;S ^TMP(""ORDATA"",$J,ORDT,""WP"",3)=""3^""_ 
$S(STAT=""d"":""Discontinued"",STAT=""c"":""Complete"",STAT=""h"":""Hold"",STAT=""p"":""Pe­nding"",STAT=""a"":""Active"",STAT=""s"":""Scheduled"",STAT=""u"":""Unreleased"", 
1:STAT) 
 ...S ^TMP(""ORDATA"",$J,ORDA,""WP"",3)=""3^""_ 
$S(STAT=""d"":""Discontinued"",STAT=""c"":""Complete"",STAT=""h"":""Hold"",STAT=""p"":""Pe­nding"",STAT=""a"":""Active"",STAT=""s"":""Scheduled"",STAT=""u"":""Unreleased"", 
1:STAT) 
 ...;S ^TMP(""ORDATA"",$J,ORDT,""WP"",4)=""4^""_$P(REC,""^"",3) 
 ...S ^TMP(""ORDATA"",$J,ORDA,""WP"",4)=""4^""_$P(REC,""^"",3) 
 ...;S ^TMP(""ORDATA"",$J,ORDT,""WP"",5)=""5^""_$$DATE^ORDVU($P(REC,""^"",4)) 
 ...S ^TMP(""ORDATA"",$J,ORDA,""WP"",5)=""5^""_$$DATE^ORDVU($P(REC,""^"",4)) 
 ...;S ^TMP(""ORDATA"",$J,ORDT,""WP"",6)=""6^""_$P(REC,""^"",5) 
 ...S ^TMP(""ORDATA"",$J,ORDA,""WP"",6)=""6^""_$P(REC,""^"",5) 
 ...;[ELN] 
 S ROOT=$NA(^TMP(""ORDATA"",$J)) 
 Q 

so I have changed the ORDT order date-time with ORDA record number.

Please review and give your comments.

Thanks."	elanchezhiyan
Active Tickets	26	Many NDC not found from file ^PSNDF(50.67) on  http://www.accessdata.fda.gov/scripts/cder/ndc/	WorldVistA EHR	2.0	milestone4	defect		new	2014-09-03T00:50:42-04:00	2014-09-03T00:50:42-04:00	"Hi,
   When we visit ^PSNDF(50.67)(NDC/UPN) many drug's NDC codes are not available on site http://www.accessdata.fda.gov/scripts/cder/ndc/
Please suggest how we can get correct drugs and how we can keep updated vista with latest updated drugs and NDC codes approved by FDA.

Thank you...
 Satish"	satish bhor
Active Tickets	9	ACRP Package crashes when reports accessed	WorldVistA EHR			defect		new	2009-11-25T18:16:42-05:00	2009-11-25T18:16:42-05:00	"> Ambulatory Care Reporting Package
> The ACRP package is very powerful and can be used to track JACHO
> monitors as well as produce reports at the Health Factor Level. The Ad
> Hoc reports are accessed at the ACRP Manager Menu.
>
> UNLESS YOUR ZU ROUTINE HAS HAS MODIFIED TO USE THIS LINE OR EQUIVALENT-
>
> > USE $I:(LENGTH=50) , YOU MUST DO THIS:
>
> gtm> USE $I:(LENGTH=50)
> gtm:>D ^ZU
>
> Otherwise the ACPR package will hang.
>
> Cameron pointed this out a couple of years ago, but I don't think the
> routine ever actually got changed. I still need to use this entry
> technique every time I access that package. This problem (apparently,
> the GT.M version of the ZU routine only allows an $I(LENGTH) to 24)
> may cause other areas to hang as well."	Matthew King
Active Tickets	3	"Resolution for ""Remote data not available - Only local order checks processed."" error message..."	WorldVistA EHR	1.0		defect		new	2009-09-29T13:06:03-04:00	2009-09-29T13:06:03-04:00	"decided to chase it, and it turns out it's due to parameter OR RDI
HAVE HDR. It's set to Yes as a default. (WV systems, for the time
being, are standalone. There is no HDR for us.) I tried to change it
to no, but the system didn't recognize the entities. I read the code;
and it turns out that its entry in the PARAMETER DEFINITION is
corrupted. You need to fix the precedence multiple, and put system and
package there; system lower than package in precedence as per
convention.

I just tried CPRS, and I no longer get the annoying message.
"	Sam Habiel
Active Tickets	11	Robust hashes for XUSHSH	WorldVistA EHR			enhancement		new	2010-01-08T12:41:25-05:00	2010-01-08T12:41:25-05:00	Utility to replace Vista's XUSHSH routine with one able to provide robust hashing for ACCESS CODE / VERIFY CODE using gnupg gpg.	John Leo Zimmer
Active Tickets	2	Upper case access verify codes	WorldVistA EHR			defect		new	2009-09-25T01:03:23-04:00	2009-10-30T14:32:26-04:00	"Although the access and verify codes are usually case insensitive,
> there is one exception. That is when you must (or decide to) change
> your verify code, then you must '''start''' your login with your original
> access/verify code in UPPER CASE. If you don't do this, VistA will not
> accept your code change even if you switch to caps to do it."	Matthew King
