Difference between revisions of "Bed Management"

From IHE Wiki
Jump to navigation Jump to search
Line 7: Line 7:
  
  
'''Summary'''  
+
=='''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:
 
''''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
 
*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 departments within the hospital occur
+
*Delays in patient transfers to other inpatient hospital departments occur
*Siloed data which results in poor data quality for process and performance improvement activities and care coordination   
+
*Siloed data which results in:
 +
**Poor data quality for process and performance improvement activities
 +
**Inability to effectively perform care coordination   
  
  
Line 18: Line 22:
  
  
==Benefits==
+
=='''Benefits'''==
  
A robust, integrated bed management not only improves patient care, but also impacts a hospital's financial status. The benefits of this profile is:
+
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
 
* Increased efficiency
Line 26: Line 30:
 
* Improved patient transfer and care coordination data, resulting in better predictive planning
 
* Improved patient transfer and care coordination data, resulting in better predictive planning
  
==Details==
+
=='''Details'''==
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
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.
  
''<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.>''
 
 
''<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==
+
=='''Systems Affected'''==
  
  
Line 40: Line 42:
 
* ''Admission/Discharge/Transfer (ADT) System''
 
* ''Admission/Discharge/Transfer (ADT) System''
 
* ''Emergency Department Information System (EDIS)''
 
* ''Emergency Department Information System (EDIS)''
* '''BMS'''
+
* '''Bed Management System (BMS)'''
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
Line 52: Line 54:
 
'''Documents:'''  
 
'''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.>''
+
''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.''
  
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
[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:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
 
:* [http://dicom.nema.org DICOM]
 
 
:* [http://www.hl7.org HL7]
 
:* [http://www.hl7.org HL7]
:* ...
+
:*  
 
 
==See Also==
 
 
 
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 
  
  
 
'''Related Profiles'''
 
'''Related Profiles'''
  
''<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.>''
+
''None. ''
 
 
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
* ''[[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'''
 
 
 
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>''
 
 
 
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>''
 
  
'''Reference Articles'''
 
  
''<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. >''
 
  
  

Revision as of 14:59, 2 March 2018


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


ED pic for BED.png


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:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: [[Comments| 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 Radiology Technical Framework:


Underlying Standards:


Related Profiles

None.




This page is based on the Profile Overview Template