[MEDITECH-L] Daily Nursing Station Census Summary from Data Repository

[Cecil, Jason]

I am working on a web-based reporting dashboard that will have many
common reports in it including our daily census. I am trying to gather
this data from our data repository but there is one report I am having
difficulty getting the results to match up. That report is the daily
nursing station census summary.

Most of the data in that report maps to the AdmStatsLocation table in
the DR. However, the beginning census, pending, and ending census are
not in that table and I am unable to find those numbers anywhere in the
DR. It appears those numbers are calculated but I haven't been able to
determine exactly how.

I have been able to duplicate other census reports by scheduling the
query to run at the same time as our midnight run but I have been unable
to form a query that will match the data for these fields.

Does anyone have any insight as to how those fields are calculated or
have a DR query they'd be willing to share?

Jason Cecil, PMP

Clinical Applications Manager

Information Technology

Capital Region Medical Center

http://www.crmc.org

====================================

Please do NOT send messages that ask "Please post to the list" These are useless messages that just waste the email server's resources. Instead, email the original requester and ask that they send you or post the results of their question.

To UNSUBSCRIBE, go to http://MTUSers.net
for information.

The meditech-l archives (and other tips) can be found at
http://mtusers.net/zarchives

Job opportunites in the Meditech community can be found at
http://mtusers.net/zjobs

[medi...@acmeware.com]

Hi Jason,

It sounds like you might be looking for the AdmNursingCensus table. This
will give you the location of each patient in a room/bed at midnight. I've
not matched this up with the standard report but I would be surprised if
this was not the right table. Good luck and hope this helps!

Jamie

Jamie McDonald
Acmeware, Inc.
781-329-4300 ext. 203
781-329-0020 (f)
www.acmeware.com

[Cecil, Jason]

I have attempted several queries from this table. The first was a
simple count by location. The numbers were within a patient or two but
never seemed to match. The second query was a count that subtracted
observation patients which I determined by joining to the AdmVisits
table. This one comes very close but the totals still don't always
match.

I appreciate the feedback.

Jason Cecil, PMP
Clinical Applications Manager
Information Technology
Capital Region Medical Center

Ph: 573-632-5112
http://www.crmc.org

[Ganesh Seshadri]

DR aside, I'm curious if, in general, you can get totals to exactly
match between reports from a stats dpm and summaries created from
details. Just recently someone wanted some census stats by unit, which
I did out of adm.patient.file using adm.pat.nurse.census.index (Magic
5.6). I then ran it for a month and tried to match against the standard
ADM stats reports - Inpatient Location figures for OBS and IP, and the
latter was consistently about a half % higher. The handicap I have
comparing against something that's stored only in summary form is that
there's no way to drill down to check for discrepancies. Eg. does one
count a same day admit/disch as a patient day while the other tallies
strictly by what's the bed status at midnight, or are LOA patients
counted differently. When you throw DR into the mix, I'm assuming
there's another dimension of potential discrepancies that'll keep you
from a bullseye.

Ganesh Seshadri
Analyst, Indiana Regional Medical Center
(724) 357-7012

[Robert White]

I am convinced that when you save the same data in different places over periods of time you will always get discrepancies.

>>> Ganesh Seshadri <gses...@indianarmc.org> 6/16/2009 2:00 PM >>>

I appreciate the feedback.

Hi Jason,

Jamie

Jason Cecil, PMP

Clinical Applications Manager

Information Technology

Capital Region Medical Center

http://www.crmc.org

====================================

====================================

====================================

====================================

Disclaimer: The information in this message is confidential. If you are not the intended recipient, do not disclose, copy, or distribute this message, and please immediately contact the sender.