Re: Can I make a form to print fields on a hcfa 1500 ins.form?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Tim,
Our systems are not going to be connected to the internet so there is no
chance of leak there. Our patient records are kept in their own personal
charts. Basically what we want to do is keep track of patient billing
information, address phone, visits listing only the date and diagnosis code
and their ins. From there I would want to be able to send a paper claim to
the ins. company and that is why I wanted to know if I could set up a format
to print information on a hcfa form ie load the hcfa forms in the printer and
have my form in my data base print the needed fields on the form. I don't do
electronic billing so it is not subject to hippa. This system would not be
used for labs and any medical information that could in turn cause harm. It
is very basic stuff. I realize that there are systems on the market, our
problem is that our doc is most likely going to retire in several months and
we don't want to make a huge investment. "Tim Ferguson" wrote:

> "=?Utf-8?B?UlMgUGVkaWF0cmljIE1lZGljYWwgUHJhY3RpY2U=?="
> <RSPediatricMedicalPractice@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> news:A1E7346F-B325-45B0-B214-11521636BB17@xxxxxxxxxxxxx:
>
> >> > I work for a physician's office and want to use Access 2003 to
> >> > manage our patient accounts.
>
> >> 3) Is it legal to do it - depends on local data protection
> >> legislation and on your answer to (2).
>
> > Thanks for answering my post. I just finished the course on Microsoft
> > Access 2003 and I now need to work with it to reinforce what I've
> > learned. Our office at work is losing it's connection of Medi-soft
> > because the hospital that we are affliated with is closing it's
> > service. From what I am aware of in Access, I thought it might be an
> > answer, however I need guidance in doing it. Do you know where I
> > could find this guidance or who I should contact?
>
> If you are taking up db design from scratch, you need to ask yourself
> some serious questions. If you screw up, are real patients going to get
> sick or die? Are they going to be bankrupted by being sent the wrong
> bill? Are the doctors going to get sued because they are sent the wrong
> medical details?
>
> I am writing from the UK where the legislative environment is somewhat
> different from the USA(?). Googling for "HIPAA" would seem to be a good
> start; you do need to know that you are capable of staying within the
> law.
>
> Finally, with a load of software available off-the-shelf, are you really
> sure that the huge amount of your time (learning, designing, coding,
> scrapping it and starting all over again, DC al coda) will really be
> cheaper than buying in something that works, where another company will
> take all the risk, which is guaranteed to be legal, etc etc?
>
> Sorry if this sounds like a dampener. I am all for people taking up and
> learning about db design, and Access is a great model to learn on (and to
> produce on, for that matter). But I also feel that some situations are a
> bit too serious to start on. Nobody learns to drive in an ambulance with
> a sick child in the back; you use a bashed-up old Fiat, so that when you
> crash and burn it's not quite such a disaster.
>
> All the best
>
>
>
> Tim F
>
>
>
.

Relevant Pages