Re: [Gnumed-devel] proposal for HL7 v2.3 to gnumed parsing

[J Busser]

At 8:38 PM +0800 5/12/05, Syan Tan wrote:
>  as parsing hits PID,
>
>  patient_name , date_of_birth  is used to match a patient.
>  If no match, match to dummy "unmatched" patient.
>  Result is a pk_identity for later use.

At 5:06 PM +0200 5/12/05, Karsten Hilbert wrote:
> What if several matches occur ?

Surely there will be at least one extra id, either some kind of 
"health identifier" usually specific to the patient. This number 
might not be specific when assigned to designate a family (though 
there may be a health "sub" number or "dependent" number) and the 
uniqueness would fall apart if after termination of the account the 
number gets re-used. Also a liability if numbers from two different 
organizations happen to be the same.

The extra "id", if not a "health identifier", could be an originating 
doctor's office tracking number (request_id) which I believe is 
assigned in Germany and might occur in other countries. This could 
indirectly serve to identify the patient to whom the specimen 
belonged, yes?

>  parsing Hits OBR,
>  if the message has ordering_provider field, which has a form
>  (id, title, firstname, lastname) , then an attempt is made
>  to match in v_staff
>  also attempt to match to each ~ separated provider
>  in results_copies_to field, if it exists.
>  If no match, then ? match to staff who has corresponding current_user name?
> Either that, yes, or - however a lot more complicated - try
> matching the time to an encounter and get the staff from that
> encounter.

Or again, there may be a "provider number" (external_id in 
lnk_identity2ext_id) but GNUmed to would need to be instructed or 
figure out which key to use among those in enum_ext_id_types --- it 
cannot necessarily infer it from the pathology org that is providing 
the results because the pathology org will likely use some other 
external identifier (not maintain its own pk) for the doctor.