In 399 there is "RESPONSIBLE INSTITUTION", as well as PRIMARY INSURANCE
CARRIER, SECONDARY INSURANCE CARRIER, and TERTIARY INSURANCE CARRIER.

In the AR package the 430 file points to the AR DEBTOR file which has a
variable pointer to multiple files for who is the responsible party.

On Sunday 08 January 2006 03:15 pm, Nancy Anthracite wrote:
Greg Woodhouse and I were working on exactly this problem just recently, and
someone gave us a suggestion for a field that was buried in a somewhat
obscure place to get this data.  It was a place that I frankly did not think
would usually be populated, but might be used anyway because we were looking
at what to do for an interface with LabCorp that any VistA user could pick up
and install.  I will go look at our notes if you are interested, but we had
not made a decision on what to use.

Let me see if I can find out what the VOE programmers did.

On Sunday 08 January 2006 02:55 pm, Kevin Toppenberg wrote:
I am working on porting demographic data from our billing software into
VistA
We have a field called RESPONSIBLE PARTY, name and address etc.  We would
use it if the patient was a minor, and we needed to record the information
for the person (different from the patient) who will be responsible for
payment.

As I look through the PATIENT field, I see lots of fields that could
possible be used for this.  For example, .223 K-STREET ADDRESS, and .2125
K-ADDRESS SAME AS PATIENT'S?

Is this issue addressed in VistA, and if so, which field should I use for
this data?

Thanks
Kevin

-- 
Nancy Anthracite


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to