Bed Management: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Ddowning (talk | contribs)
No edit summary
JohnMoehrke (talk | contribs)
 
(39 intermediate revisions by one other user not shown)
Line 1: Line 1:
'''This is a template page.  [[:Category:Templates|CLICK HERE]] if you're not sure how to use it.  DO NOT MODIFY this page unless you are changing the template for all future users.'''


This profile is to manage the interoperability issues that surround the bed management tasks that are involved with admissions to the various hospital departments from the emergency department.


''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
__TOC__


''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''


=='''Summary'''==


''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''


''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
[[image: ED pic for BED.png|300px]]


__TOC__


==Summary==
''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''


''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
Bed management is the ability for a healthcare facility or system to have real-time operational awareness of the status of all of its available beds and to be able to plan for the expedient use of beds through coordination of the bed turnover process. Beds are a scarce resource, and the limitation of access to beds leads to delays and waste within healthcare systems.


''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
'''Due to a lack of interoperability in the emergency department several problems occur:
*Work inefficiencies are decreased for emergency department providers and other staff with no mechanism to monitor patient status in real-time
*Delays in patient transfers to other inpatient hospital departments occur
*Siloed data which results in:
**Poor data quality for process and performance improvement activities
**Inability to effectively perform care coordination


==Benefits==
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''


==Details==
=='''Benefits'''==


''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
A robust, integrated bed management process not only improves patient care, but also impacts a hospital's financial status. The benefits of this profile are:


''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
* Increased efficiency
* Reduced delays and waste
* Improved patient transfer and care coordination data, resulting in better predictive planning


''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
==Systems Affected==
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''


* ''PACS systems may store, manage, and/or display Evidence Documents.''
=='''Details'''==
* ''Display systems may query, retrieve and display Evidence Documents.''
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports


'''Actors & Transactions:'''
This transport profile facilitates bed management for patients admitted from the ED. Inefficiencies in transferring patients between the emergency department and inpatient setting result in poorer patient outcomes (e.g., morbidity, mortality or length of stay), increased patient dissatisfaction and poorer resource utilization in the ED. This profile describes how communications between the ED and various inpatient systems can improve care, reduce cost and result in higher patient satisfaction, and enable tracking and monitoring of these activities to support quality improvement activities.
This profile does not address how charge information is transferred from various involved systems to the back office, or how discharge or transfers from the inpatient setting to other settings are handled.


''<Insert an actor-transaction diagram, and or list of Content Definitions>''
=='''Systems Affected'''==


==Specification==


'''Profile Status:''' [[Comments| Final Text]] 
* ''Electronic Health Record (EHR)''
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
* ''Admission/Discharge/Transfer (ADT) System''
* ''Emergency Department Information System (EDIS)''
* ''Bed Management System (BMS)''


'''Documents:'''


''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
== '''Actors & Transactions:''' ==


[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E


'''Underlying Standards:'''
''''[[Image:BED ActorTransaction Diagram.png|550px]]


''<list all the standards on which the profile is based; if possible with links to sources>''
=='''Specifications'''==
:* [http://dicom.nema.org DICOM]
:* [http://www.hl7.org HL7]
:* ...


==See Also==
'''Profile Status:  '''Trial Implementation''


''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''


'''Documents:'''


'''Related Profiles'''
The BED Profile is designed to work alongside the IHE IT Infrastructure PAM Profile, but has differing requirements upon what actors are used and additional requirements for the messages that they send.


''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''


* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
* IHE ITI Patient Administration Management Profile  [http://wiki.ihe.net/index.php/Patient_Administration_Management:]
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''




'''Consumer Information'''
'''Underlying Standards:'''


The [[Profile FAQ Template]] answers typical questions about what the Profile does. ''<Replace the link with a link to the actual FAQ page for the Profile>''
:* HL7 v2.6 ADT, Patient Administration [http://www.hl7.org HL7]
:* HL7 EDIS Functional Profile - Registration Release 1 (v.1.4)


The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''


'''Implementer Information'''


The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
'''Related Profiles'''


'''Reference Articles'''
''None. ''


''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''




Line 97: Line 80:
This page is based on the [[Profile Overview Template]]
This page is based on the [[Profile Overview Template]]


[[Category:Profiles]][[Category:Patient Care Coordination]][[Category: HL7 v2.5]]
[[Category:Profiles]][[Category:Patient Care Coordination]][[Category:HL7v2]]

Latest revision as of 10:14, 4 November 2019

This profile is to manage the interoperability issues that surround the bed management tasks that are involved with admissions to the various hospital departments from the emergency department.


Summary


Bed management is the ability for a healthcare facility or system to have real-time operational awareness of the status of all of its available beds and to be able to plan for the expedient use of beds through coordination of the bed turnover process. Beds are a scarce resource, and the limitation of access to beds leads to delays and waste within healthcare systems.

Due to a lack of interoperability in the emergency department several problems occur:

  • Work inefficiencies are decreased for emergency department providers and other staff with no mechanism to monitor patient status in real-time
  • Delays in patient transfers to other inpatient hospital departments occur
  • Siloed data which results in:
    • Poor data quality for process and performance improvement activities
    • Inability to effectively perform care coordination


Benefits

A robust, integrated bed management process not only improves patient care, but also impacts a hospital's financial status. The benefits of this profile are:

  • Increased efficiency
  • Reduced delays and waste
  • Improved patient transfer and care coordination data, resulting in better predictive planning


Details

This transport profile facilitates bed management for patients admitted from the ED. Inefficiencies in transferring patients between the emergency department and inpatient setting result in poorer patient outcomes (e.g., morbidity, mortality or length of stay), increased patient dissatisfaction and poorer resource utilization in the ED. This profile describes how communications between the ED and various inpatient systems can improve care, reduce cost and result in higher patient satisfaction, and enable tracking and monitoring of these activities to support quality improvement activities. This profile does not address how charge information is transferred from various involved systems to the back office, or how discharge or transfers from the inpatient setting to other settings are handled.


Systems Affected

  • Electronic Health Record (EHR)
  • Admission/Discharge/Transfer (ADT) System
  • Emergency Department Information System (EDIS)
  • Bed Management System (BMS)


Actors & Transactions:

'

Specifications

Profile Status: Trial Implementation


Documents:

The BED Profile is designed to work alongside the IHE IT Infrastructure PAM Profile, but has differing requirements upon what actors are used and additional requirements for the messages that they send.


  • IHE ITI Patient Administration Management Profile [1]


Underlying Standards:

  • HL7 v2.6 ADT, Patient Administration HL7
  • HL7 EDIS Functional Profile - Registration Release 1 (v.1.4)


Related Profiles

None.



This page is based on the Profile Overview Template