Re: Archetype-based querying in GEHR

David W Forslund Thu, 05 Apr 2001 12:02:22 -0700
This leads to a question that has been occurring to me.  When I look at
the RDF-Schema from W3C (and to a lesser extent, XMI from the CWM work
at the OMG), it seems to me that it is an ideal way to express templates
or archetypes.   (Since it has been shown that one can map from RDF to
XMI, this would be equivalent to using XMI).  I'm wondering why the HL7
folks aren't using RDF, since it lets one express relationships between
classes and objects very nicely.  The advantage of using XML is that the
querying can then be done using the powerful XPath tools.

Dave
Thomas Beale writes:
 > 
 > Greetings all,
 > 
 > As a one-off, I have decided to publish a small indication of where GEHR
 > is going with respect to querying.
 > 
 > Many people ask how GEHR supports queries, and how is data extracted
 > from the EHR. Not much documentation has been produced on this subject
 > to date, because the querying system for GEHR is quite different from
 > other systems, due to the use of archetypes.
 > 
 > However, to give an idea of how one category of query will work, I have
 > included an example below. The technical basis for queries with
 > archetypes is that: every archetype has an "archetype query profile",
 > which is a sort of inverted list of all possible paths in the archetype,
 > keyed by leaf node name. For example, the query profile for a blood
 > pressure observation archetype is as follows:
 > 
 > ------ Archetype Query Profile: gehr.cont-observe.blood_pressure.v1
 > ------------------
 > Diastolic:                               |"blood pressure"|"Diastolic"
 > Systolic:                                |"blood pressure"|"Systolic"
 > blood pressure:                          |"blood pressure"
 > 
 > Here, the first column contains tag names which applications are likely
 > to want to search for in patient data. The path fragments on the right
 > hand side can be attached to the paths for higher up archetypes (e.g.
 > which ever archetype was used to construct the organisers containing the
 > BP), and submitted to the query engine, in order to extract a particular
 > datum from the record. This list was derived automatically from the
 > blodd pressure archetype.
 > 
 > Here are a couple more examples:
 > 
 > -------- Archetype Query Profile: gehr.org.soap.v1 ------------------
 > Plan:                                    /"SOAP
 > Headings"/"Problem"/"Plan"
 > Objective:                               /"SOAP
 > Headings"/"Problem"/"Objective"
 > Subjective:                              /"SOAP
 > Headings"/"Problem"/"Subjective"
 > Assessment:                              /"SOAP
 > Headings"/"Problem"/"Assessment"
 > SOAP Headings:                           /"SOAP Headings"
 > Problem:                                 /"SOAP Headings"/"Problem"
 > 
 > ---- Archetype Query Profile: gehr.cont-subj.allergies.v1
 > ------------------
 > Date:                                    |"Allergies"|"Date"
 > Code:                                    |"Allergies"|"Code"
 > Code set:                                |"Allergies"|"Code"|"Code set"
 > Allergies:                               |"Allergies"
 > Substance name:                          |"Allergies"|"Substance name"
 > Drug code:                               |"Allergies"|"Code"|"Drug code"
 > 
 > Type:                                    |"Allergies"|"Type"
 > Comment:                                 |"Allergies"|"Comment"
 > Scope:                                   |"Allergies"|"Scope"
 > 
 > Notice that organiser-level archetype paths are "/" delimited, content
 > paths are "|" delimited.
 > 
 > For people wishing to discuss querying, please use
 > mailto:[EMAIL PROTECTED] (or else the open source discussion
 > list).To subscribe to gehr-discuss, go to
 > http://www.egroups.com/group/gehr-discuss
 > 
 > - thomas beale
 > (for the GEHR team)
 > 
 > <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 > <html>
 > &nbsp;
 > <br>Greetings all,
 > <p>As a one-off, I have decided to publish a small indication of where
 > GEHR is going with respect to querying.
 > <p>Many people ask how GEHR supports queries, and how is data extracted
 > from the EHR. Not much documentation has been produced on this subject
 > to date, because the querying system for GEHR is quite different from other
 > systems, due to the use of archetypes.
 > <p>However, to give an idea of how one category of query will work, I have
 > included an example below. The technical basis for queries with archetypes
 > is that: every archetype has an "archetype query profile", which is a sort
 > of inverted list of all possible paths in the archetype, keyed by leaf
 > node name. For example, the query profile for a blood pressure observation
 > archetype is as follows:
 > <p><tt>------ Archetype Query Profile: gehr.cont-observe.blood_pressure.v1
 > ------------------</tt>
 > 
 ><br><tt>Diastolic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"blood pressure"|"Diastolic"</tt>
 > 
 ><br><tt>Systolic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"blood pressure"|"Systolic"</tt>
 > <br><tt>blood 
 >pressure:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"blood pressure"</tt>
 > <p>Here, the first column contains tag names which applications are likely
 > to want to search for in patient data. The path fragments on the right
 > hand side can be attached to the paths for higher up archetypes (e.g. which
 > ever archetype was used to construct the organisers containing the BP),
 > and submitted to the query engine, in order to extract a particular datum
 > from the record. This list was derived automatically from the blodd pressure
 > archetype.
 > <p>Here are a couple more examples:
 > <p><tt>-------- Archetype Query Profile: gehr.org.soap.v1 ------------------</tt>
 > 
 ><br><tt>Plan:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > /"SOAP Headings"/"Problem"/"Plan"</tt>
 > 
 ><br><tt>Objective:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > /"SOAP Headings"/"Problem"/"Objective"</tt>
 > 
 ><br><tt>Subjective:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > /"SOAP Headings"/"Problem"/"Subjective"</tt>
 > 
 ><br><tt>Assessment:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > /"SOAP Headings"/"Problem"/"Assessment"</tt>
 > <br><tt>SOAP 
 >Headings:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > /"SOAP Headings"</tt>
 > 
 ><br><tt>Problem:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > /"SOAP Headings"/"Problem"</tt>
 > <p><tt>---- Archetype Query Profile: gehr.cont-subj.allergies.v1 
 >------------------</tt>
 > 
 ><br><tt>Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Date"</tt>
 > 
 ><br><tt>Code:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Code"</tt>
 > <br><tt>Code 
 >set:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Code"|"Code set"</tt>
 > 
 ><br><tt>Allergies:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"</tt>
 > <br><tt>Substance 
 >name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Substance name"</tt>
 > <br><tt>Drug 
 >code:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Code"|"Drug code"</tt>
 > 
 ><br><tt>Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Type"</tt>
 > 
 ><br><tt>Comment:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Comment"</tt>
 > 
 ><br><tt>Scope:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 > |"Allergies"|"Scope"</tt>
 > <p>Notice that organiser-level archetype paths are "/" delimited, content
 > paths are "|" delimited.
 > <p>For people wishing to discuss querying, please use <a 
 >href="mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]</a>
 > (or else the open source discussion list).To subscribe to gehr-discuss,
 > go to <a 
 >href="http://www.egroups.com/groups/gehr-discuss">http://www.egroups.com/group/gehr-discuss</a>
 > <p>- thomas beale
 > <br>(for the GEHR team)
 > <br>&nbsp;</html>
Re: Archetype-based querying in GEHR

Reply via email to
