Alvin
This is the simplest form of architecture that was agreed in the early
nineties at CEN. It is only likely to have value in the messaging arena
where it is already the standard (HL7 and Australia).
The problem domain is much larger than this and needs to be seen as such if
we are to make any progress. I for one cannot rejoice at being somewhere I
was 15 years ago! The only difference is that LOINC are doing what European
GEHR project and Health.one did quite a while ago - with more resources and
a less formal approach.
Anyway - lets do that but lets do a little more if we want to share EHRs!
Cheers, Sam
____________________________________
Sam Heard
Director, General Practice Education and Research Unit
Northern Territory Clinical School, Flinders Univeristy
PO Box 41326, Casuarina, NT 0811
RACGP Training Program
Northern Territory Regional Office
Ph: (08) 8922 7937
Fx: (08) 8922 7928
Email - [EMAIL PROTECTED]
Web - gperu.flinders.edu.au
The Good Electronic Health Record
www.gehr.org
___________________________________
----- Original Message -----
From: "Alvin B. Marcelo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 18, 2000 8:23 AM
Subject: A Proposal
> I would like to make a proposal to the alliance:
>
> Given that:
>
> we can't agree on data models
> we can't agree on prgramming language
> we can't agree on platforms for interoperability...
>
> (and this is all fine because the technology is not that mature) [read as:
> no randomized trial to support any of them :) ]
>
> My proposal is that we agree _simply_ on data element _semantics_.
>
> PROPOSAL:
>
> All OSHCA projects (upcoming) will agree to use LOINC codes to identify
> their data elements OR agree to map their current local data elements to
> LOINC (ongoing).
>
> Wherever possible, use UMLS CUI's for data values. So name=value pair will
> be LOINC code=UMLS CUI.
>
> It's clean and simple. Just LOINC (we can bypass UMLS if there's issue).
> It's in plain ASCII and it's free.
>
> All you need is build a LOINC table into your app (or the subset you
need).
> And another table where you can keep your mappings (if needed).
>
> By doing so:
>
> No one is compelled to use any programming language.
> No one is compelled to use any database management system.
> We agree on using LOINC as our Esperanto.
>
> It doesn't solve all our problems, but it does give us a neutral, common
> ground where we can start collaborating. And we don't reinvent anything
> (Regenstrief-NLM will do the hard work.)
>
> Comments please. If you disagree, please explain why and please provide a
> better (and as quick) solution.
>
> Please, someone tell me this can work.
>
> 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
>
>
