All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Frank:
I wholeheartedly agree. To facilitate this, we use "dummy" CDSs to
print the data. With some forethought, you can avoid the printouts from
looking like the patient has a ventilator, when you documented oxygen or
pulse ox.
For example: We have interventions (with unique CDSs) for:
Oxygen
Pulse Ox
Ventilator
RT, Ventilator Maint
Each of these CDSs have the same query for Pulse OX %
To print this, our profile has the "dummy" CDS labeled "Respiratory
Management"
This CDS has all of the questions that pertain to Respiratory
Assessment.
The result is that the documentation reflects a section titled
Respiratory Management with a response to Pulse Ox. If Pulse Ox is the
only question answered, it doesn't matter which intervention the Pulse
Ox was documented from. If all of the questions pertaining to Oxygen
administration are answered also, they will also print in that column
with the pulse ox. Again, the section header is Respiratory Management,
not "ventilator" or "Pulse Ox" or "Oxygen".
I hope this helps,
Brian
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cyr Frank
Sent: Thursday, March 09, 2006 5:54 AM
To: Walker, Ann; Davis Daniel (SouthernHills); Marie-Pierre Dionne;
[EMAIL PROTECTED]
Subject: RE: [MEDITECH-L] Flowsheet from meditech Question
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
One of MEDITECH's main strengths is its integration. To get the most out
of MEDITECH, we should capitalize on its integration capabilities. One
way to accomplish this is to share queries between modules whenever
possible. Here is a basic clinical example. If the ED sends a patient
directly to the OR, and then post operatively the patient is sent to an
inpatient unit, it would be beneficial for the clinical information in
the EDM module, the OR module and the NUR module to be transferable and
reviewable in a way that supports the continuum of care and promotes
patient safety.
Sharing queries does not prevent us from isolating specific
documentation occurrences of the queries. NPR reports, macros,
attributes and other tools can isolate this data.
On the flipside of this discussion, I have seen facilities that have
illogically shared queries. For example, in most situations, a comment
query used on a patient education screen, should not be also used on a
cardiac assessment screen. This action would prevent you from being able
to isolate the patient education comments, etc...
When queries are not shared...
facilities tend to have an easier time creating isolated output
structures in reports and/or PCI. But, they end up compartmentalizing
their data, which makes it difficult to see the data flow throughout the
patient's care and to use the data in a real time environment as a care
giving tool. It also increases the odds that data could missed or
overlooked.
When queries are shared...
it is easier to see the entire picture, but more difficult to isolate
specific documentation occurrences.
My experience has led me to find it to be easier to extract isolated
documentation occurrences on a "shared query" model, than it is to try
to make a cohesive composite of a "non-shared query" compartmentalized
model.
In closing... I've seen too many times elements of compartmentalized
data get missed by care providers/physicians. This occurrences can lead
to improper care and/or to the care provider/physician no longer
trusting and/or using MEDITECH. Absence of data is a liability.
I hope this information helpful.
Frank Cyr RN
Clinical Systems Development
TriStar Division
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Walker, Ann
Sent: Wednesday, March 08, 2006 4:32 PM
To: Davis Daniel (SouthernHills); Marie-Pierre Dionne;
[EMAIL PROTECTED]
Subject: RE: [MEDITECH-L] Flowsheet from meditech Question
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
I very much agree with what Daniel said. Shared queries can cause a lot
of problems in different areas. I try to only share queries such as
V/S's, I&O, Advanced Directives, Organ Donor, etc. Shared queries cause
a lot of issues in Profiles and also when you archive profiles. I
learned that the hard way.
Ann Walker, RN, BS
Clinical Specialist II
Information Systems
Wadley Health System
Texarkana, Texas 75501
903-798-7765
-----Original Message-----
From: Davis Daniel (SouthernHills)
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 8:37 AM
To: Marie-Pierre Dionne; [EMAIL PROTECTED]
Subject: RE: [MEDITECH-L] Flowsheet from meditech Question
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Using shared queries has always had its pit falls. If you share a query
it has that same issue when pulled into PCI, when pulled into an NPR
report, when pulled into a print profile, etc. This is not a new issue,
it simply places our focus on an existing issue.
When designing documentation, queries should be shared for a specific
reason, understanding the ramifications of sharing that query.
Otherwise, I believe it would be best not to share queries.
Daniel Davis, RN
Patient Care Module Coordinator
Southern Hills Medical Center
Nashville, TN
(615) 781-4153
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Marie-Pierre Dionne
Sent: Tuesday, March 07, 2006 2:30 PM
To: [EMAIL PROTECTED]
Subject: [MEDITECH-L] Flowsheet from meditech Question
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
_______________________________________________
meditech-l mailing list
[email protected] http://mtusers.com/mailman/listinfo/meditech-l
_______________________________________________
meditech-l mailing list
[email protected] http://mtusers.com/mailman/listinfo/meditech-l
_______________________________________________
meditech-l mailing list
[email protected] http://mtusers.com/mailman/listinfo/meditech-l
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
