[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] how to do intended_reviewer / requestor? (was: HL7 te

From: lkcl
Subject: Re: [Gnumed-devel] how to do intended_reviewer / requestor? (was: HL7 test results import.)
Date: Mon, 9 Aug 2010 12:12:06 -0700 (PDT)

lkcl wrote:
> these simple changes would make it possible to absolutely guarantee the
> insertion and import of (syntactically-correct) HL7 data, as any unmatched
> patients or practitioners would go into the "unidentified" string fields. 
> by having a string array, you could even store both the copies_to and
> intended provider fields, even if _those_ were "unidentified".
> and, you would have the added advantage of not having to create "fake
> patients" or "fake staff"
> _and_, the same code and the same procedure could be used for _other_
> importers: they _too_ could "always succeed".

sorry, re-reading this, forgot to say: the end result being that for some
other importer, no additional code would be required to process semantically
"wrong" imports which likewise had incorrect or non-existent patients or
staff associated with them.  all that would need to be written would be an
importer which did the same trick of "set patient field to NULL, set
unmatched_patient instead", and the exact same
clin.lab_request+clin.test_data dialog box would use that field to a) mark
the record with "red warnings" b) present a "match with patient" or "match
with staff" dialog.

no other-importer-specific extra code would be needed to have the other
importer do patient or staff disambiguation: that job's handled by the
clin.lab_request+clin.test_data dialog box.


View this message in context:
Sent from the GnuMed - Dev mailing list archive at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]