Wendy
KU has not deployed their encounter type variable yet to my knowledge and not
all deployed data has been moved to Babel for many of our sites. KU will and
must deploy encounter type to be compliant with PCORI and participate in GPC.
So I am simply saying that all of our sites will have the data deployed and it
should be part of any data management planning. Therefore the "last completed
encounter" as a marker for "our last contact with the living patient" will be
satisfied within our GPC/PCORI common data model as:
"the last encounter of type IP, IS, AV, ED or OA" for the patient.
At UNMC at least, NO patient visit occurs that is not stored into i2b2 as an
Encounter.
We may want to visit this as a quality variable across GPC in terms of
frequency of non-documented visit activity.
Jim
________________________________________
From: GPC Informatics [d...@madmode.com]
Sent: Wednesday, November 12, 2014 12:15 PM
To: m...@wisc.edu; j...@kumc.edu; dconno...@kumc.edu; Hickman, Hubert B;
Campbell, James R
Cc: tshire...@kumc.edu; tmcma...@kumc.edu; gpc-dev@listserv.kumc.edu
Subject: Re: [gpc-informatics] #178: determine whether last.visit is the last
fulfilled visit or the last scheduled visit
#178: determine whether last.visit is the last fulfilled visit or the last
scheduled visit
-----------------------+----------------------------
Reporter: mish | Owner: jhe
Type: problem | Status: assigned
Priority: major | Milestone: data-quality2
Component: data-stds | Resolution:
Keywords: | Blocked By: 155
Blocking: |
-----------------------+----------------------------
Comment (by jhe):
Replying to [comment:7 campbell]:
Jim,
Thanks for the clarification. There is a variable called last.visit
among the demographic variables in Heron. What we wanted to find out is
whether last.visit is a fulfilled visit or not. If yes, then we know the
patient was last known alive on that day. if no, then we can't use
last.visit as last known alive date.
It is great to know that encounter type can differentiate encounters
completered and others. But this is not enough for answering the original
question. When we run a query, we pull encounters related to a specific
disease only, so the last encounter of the patient with the hospital
(likely related other diseases) may not be in the pulled data.
I don't know whether the date of last.visit corresponds to the last
encounter (among all encounters with the hospitals). If it is, then we
need to find that encounter and its type (completed or not). Dan and
Tamara: do you know whether we can do this?
If last.visit is not linked to an encounter in the system, then we are
back to the begining ot the original question: is last.visit fulfilled or
scheduled only.
Thanks,
Wendy
> Wendy
> Encounters are rolled out unequally across GPC right now. Given
differences in system installations, I suggest you consider the PCORI
common data model for encounters which we all must implement (and are
implementing or have implemented. Encounter types indicate whether
encounters are scheduled or completed:
> - ENCOUNTR TYPE (LOINC: 75525-6)
> - COMPLETED: AV=AMBULATORY VISIT; ED=EMERGENCY DEPARTMENT; IS=
NONINSTITUTIONAL INPATIENT STAY; IP=INPATIENT STAY; OA=OTHER AMBULATORY
VISIT
> - SCHEDULED OR ADMINISTRATIVE: OT=OTHER; UN=UNKNOWN; NI=NO
INFORMATION
> Our source data at UNMC has considerable more detail regarding
administrative types of encounters and you should tell us if you have
needs for tracking those types of events.
> The Completed encounter types are actual face-to-face encounters of some
type with the patient and are those you presumably what you want for
research. The others are administrative or scheduling encounters and
should be ignored for patient care issues
>
> Have I answered your question?
>
> Jim Campbell
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/178#comment:9>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
The information in this e-mail may be privileged and confidential, intended
only for the use of the addressee(s) above. Any unauthorized use or disclosure
of this information is prohibited. If you have received this e-mail by mistake,
please delete it and immediately contact the sender.
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
