At one time, Bob Mayes wanted to build a HCFA standard "reporting object" to
minimize the interpretation problems. There were some resource challenges,
then I lost track of the initiative. A HCFA-standard Reporting
Service/Facility would be a valuable Common Service (in the Common Object
Request Broker Architecture sense) to the U.S. health care industry. Note,
I'm NOT saying it should be a CORBAmed defined common service with formally
standardized interface specification. I am suggesting that, if it should
come into being, it would be prudent for it to be engineered as "CORBA
plug-in capable" as well as other API types, not the least of which is HL7.
If my leaking old memory serves, I think I did say that to Bob a few months
back.
Scott
Scott M. Eyestone, OD
Functional Co-chair, OMG/CORBAmed
Senior Research Scientist
Battelle Memorial Institute
email: [EMAIL PROTECTED]
voice: (703) 575-2119
fax: (703) 671-9180
> -----Original Message-----
> From: Mary Kratz [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, January 20, 2000 9:40 AM
> To: [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: HCFA forms
>
> Ah, the perfect application of Open Source for US vendors and providers
> alike. HCFA mandates do not add any value to a healthcare software
> application (say a finance app), but ALL US vendors must embed this logic
> in their systems, or no provider will purchase the product
> offering. Trouble is, every vendor interprets the HCFA requirements
> slightly differently. The result is that the data going to HCFA is then
> hard to interpret/use.
>
> Bob Mayes at HCFA had the vision to build a toolset to address these
> issues. MedQuest is the name of the toolset, and HCFA makes it freely
> available off the HCFA web site at http://www.hcfa.gov/medquest/medq1.htm.
>
> Bob's recent efforts focus on metadata. One quickly realizes the benefits
>
> of metadata in a complex data set, such as HCFA is responsible for. I
> believe the metadata definitions are currently being incorporated into the
>
> MedQuest offerings, but Bob would know better than I.
>
> If you *really* want the HCFA forms, you can ask HCFA for a copy. I did
> this a few year back, when I took on a position as EDI Coordinator. HCFA
> sent me a package about 15 inches of paper in depth...at least a month's
> worth of reading! Very ugly!!
>
> Hope this helps. I'm sure Bob would like feedback on MedQuest.
>
> -Mary
>
>
> At 01:00 PM 1/19/00 -0500, Alvin B. Marcelo wrote:
> >Question from an outsider:
> >
> >Which HCFA forms are providers required to submit in the US?
> >
> >Is there a way of connecting a HCFA electronic form to a database so that
>
> >appropriate fields are extracted from the database, placed on the form,
> >and then printed pdf-like _using open source tools_? I know this can be
> >done with Adobe Acrobat but is there an open source counterpart?
> >
> >Thanks.
> >
> >alvin
> >
> >
> >
> >-------------------------------------------------------------------------
> ---
> >----------
> >Alvin B. Marcelo, M.D.
> >National Library of Medicine, B1N30
> >Office of High Performance Computing and Communications
> >Bethesda, Maryland 20894
> >
> >Voice: 301-435-3278
> >Fax: 301-402-4080
> >eFax: 603-452-3657
> >
> >Work: [EMAIL PROTECTED] [EMAIL PROTECTED]
> >Home: [EMAIL PROTECTED]
> >
> >PGP keyID: 0x6E9941D1
> >PGP server: http://www.keyserver.net
