Tracking insurance claims/medical info

[Ross Boylan]

On Mon, Apr 22, 2002 at 02:32:10PM -0400, Derek Atkins wrote:
> Sounds like a job for a co-resident Database, where multiple

I'm not familiar with the term "co-resident database."  What does it
mean? To me the structure of the problem seems more like one where
there might be several databases (gnucash's being one) and you want
the transaction to span the databases.

Or do you mean transaction in the financial, rather than database,
sense?

> applications feed into a single database and "transactions" can move
> from one application to another.
> 
> I don't think Gnucash is necessarily the right starting point for this
> marriage, but I could be wrong.
> 
> Some of this might be doable with the Invoice and Lot handling that
> is/will-be in CVS.

Is there a description of that anywhere?

Thanks.

> 
> -derek
> 
> Ross Boylan <RossBoylan@stanfordalumni.org> writes:
> 
> > I am interested in tracking medical insurance claims.  As far as I can
> > tell, gnucash doesn't really do this, and it's not an active project.
> > Is that right, or have I overlooked something?
> > 
> > Does anyone have any thoughts about whether it would be appropriate to
> > add something to do this to gnucash, and what approach to take?
> > 
> > Note that this area involves three quite different domains:
> > 1) writing and receiving money (i.e, gnucash's core function)
> > 2) tracking the submission of insurance claims, with the many
> > complexities attendant to that (multiple rounds, multiple insurers,
> > copayments, etc, etc).
> > 3) tracking health and illness, doctor visits, immunizations.
> > 
> > Since the U.S. is the only industrial country without national health
> > insurance, area 2 is probably of only limited international interest.
> > Lucky you if you don't live in the US and have to deal with the
> > incredible swamp of our health/insurance system.
> > 
> > I think this is kind of an interesting design problem, as it
> > represents a kind of problem that has its own set of requirements, but
> > has some overlap with gnucash.  It would be nice to avoid the hassle
> > of having to enter information twice in two separate programs.  But,
> > as I say, I'm not sure if there's a good way to do it.
> > 
> > Thanks.
> > _______________________________________________
> > gnucash-devel mailing list
> > gnucash-devel@lists.gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>