Scribd
Upload
73 views4 pages

Hospital Information System Requirements - Project 2

This document discusses requirements for integrating a new hospital information system called BedBoard with downstream systems. It provides background on the system and describes five registration/admission, discharge, and transfer events that can occur in BedBoard. It also lists the HL7 message triggers that will be used to transmit data to other systems. The document then provides sample message profiles for patient transfer, discharge and update events, detailing the required and optional fields for each. It concludes with requirements for a PID segment profile specifying which fields are required, optional, or not supported in the sending system.

Uploaded by

07031981
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
73 views4 pages

Hospital Information System Requirements - Project 2

This document discusses requirements for integrating a new hospital information system called BedBoard with downstream systems. It provides background on the system and describes five registration/admission, discharge, and transfer events that can occur in BedBoard. It also lists the HL7 message triggers that will be used to transmit data to other systems. The document then provides sample message profiles for patient transfer, discharge and update events, detailing the required and optional fields for each. It concludes with requirements for a PID segment profile specifying which fields are required, optional, or not supported in the sending system.

Uploaded by

07031981
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences &Technology 4006-430 Medical

l Application Integration Project 2

Hospital Information System Requirements Project 2


Background Information Lake Ontario Medical Center (LOMC) is installing a new ADT Registration system. The application is called BedBoard and it was developed by expert software developers from LOMC. Several registration / ADT events may occur such as 1) A patient can be admitted to the hospital into a nursing unit - room / bed 2) The nurse can transfer a patient to a different bed. 3) The nurse can discharge the patient (send the patient home). 4) The registration clerk can update patient information such as insurance information. 5) The medical records data integrity manager can merge a patient. This occurs when the registration clerk creates a duplicate patient. A merge associates all patient information updates from the duplicate patient into the correct patient and deactivates the duplicate patient identifier. Trigger Events BedBoard will process and transmit the following HL7 ADT events to the downstream systems (Lab, Pharmacy, Radiology, CPOE, CDR) A01 Inpatient Patient Admission A02 Inpatient Patient Transfer Location A03 Patient Discharge A05 Patient Pre-Admit (typically used for predetermined operations or obstrectics) A06 Transfer from ED to Inpatient A08 - Patient Update A11 Cancel Admit A12 Cancel Transfer A13 Cancel Discharge A28 Create Patient MPI A31 Update Patient MPI A34 Transfer Patient Account from MRN A to MRN B A36 Deactivate MRN A Merge into MRN B

Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences &Technology 4006-430 Medical Application Integration Project 2

Message Profile The following message profile is in compliance with HL7 v2.5 specifications. It conforms to the following structure
ADT^A01 MSH EVN PID [ PD1 ] [{ ROL }] [{ NK1 }] PV1 PV2 ROL DB1 OBX AL1 ADT Message Message Header Event Type Patient Identification Additional Demographics Role Next of Kin / Associated Parties Patient Visit Patient Visit - Additional Info. Role Disability Information Observation/Result Allergy Information Diagnosis Information Diagnosis Related Group Procedures Role Guarantor Insurance Insurance Additional Info. Insurance Additional Info - Cert. Role Accident Information Universal Bill Information Universal Bill 92 Information Patient Death and Autopsy Usage R R R X X RE R R X X X RE X X X X X X RE R RE X X RE X X X Cardinality [1..1] [1..1] [1..1] [0..0] [0..0] [0..10] [1..1] [1..1] [0..0] [0..0] [0..0] [0..*] [0..0] [0..0] [0..0] [0..0] [0..0] [0..0] [0..3] [1..1] [0..1] [0..0] [0..0] [0..1] [0..0] [0..0] [0..0] Chapter 2 3 3 3 12 3 3 3 12 3 7 3 6 6 6 12 6 6 6 6 12 6 6 6 3

[ [{ [{ [{ [{

] }] }] }] }]

[{ DG1 }] [ DRG ] [{ PR1 [{ ROL }] }] [{ GT1 }] [{ IN1 [ IN2 ] [{ IN3 }] [{ ROL }] }] [ ACC ] [ UB1 ] [ UB2 ] [ PDA ]

Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences &Technology 4006-430 Medical Application Integration Project 2

Project 2 - Assignment 1. Develop Message Profiles to support the following: a. Transfer Patient b. Discharge Patient c. Update Patient
ADT^________ ADT Message Usage Cardinality

For each message profile use the header above as a template. Remember to fill in the blank for the HL7 2 event type for each message profile. Required Segments for all three message profiles will be: a. MSH b. EVN c. PID For Update Patient the PV1 segment is also required All required segments must have a cardinality that requires one and only one occurrence. Optional Segments For Transfer Patient the PD1 segment is optional. This segment may be absent or it may be present with one occurance. For Discharge Patient the DG1 segment is optional and repeating. This segment may occur from zero to 5 times. Also, the AL1 segment is optional and repeating. This segment may occur from zero to an unlimited number. For Update Patient Optional requirements for Transfer Patient and Discharge Patient apply. Plus, the insurance information is optional. If insurance information is sent, then the IN1 segment must appear first. Next, the IN2 segment is optional with a zero to one cardinality. Finally, the IN3 segment is optional and may occur up to 5 times. NOTE: Use the A01 message profile displayed on the previous page for guidance and message profile conformance. Segments must appear in the order based on the A01 message profile for transfer, discharge and update patient. You task is to trim down and adjust the message profiles based on the requirements.

Rochester Institute of Technology Golisano College of Computing and Information Sciences Department of Information Sciences &Technology 4006-430 Medical Application Integration Project 2

2. Develop a Segment Profile for a PID Segment with the following rules: a. Fields 1 required 2 not supported not used by sending system 3 required, one and only one 4 not supported not used by sending system 5 required, one and only one 6 required but may be empty, cardinality of zero or 1 7 required, one and only one 8 required, one and only one 9 not supported not used by sending system 10 required, one and only one value 11 required but may be empty, if sent, one and only one 12 not supported 13 required, may be empty, no more than 2 14 - required, may be empty, no more than 2 15 not supported 16 required, may be empty, no more than 1 17 required, may be empty, no more than 1 18 required, one and only one value 19 not supported 20 not supported 21 not supported 22 not supported 23 not supported 24 not supported 25 not supported 26 not supported 27 not supported 28 not supported 29 required but may be empty, if present, only 1 occurance 30 not supported Use the lecture slides as a template along with the following table header. SEQ Sequence number (valid values are 1 30) LEN - Length of field use values found in lecture slides DT Data Type use values found in lecture slides Usage R Required, RE Required Exception, O Optional, C Conditional Use lecture slides for all possible values / meanings. Cardinality [0.0], [0.1], [1.5], [1.*] Use lecture slides for possible values.
SEQ LEN DT Usage Cardinality ELEMENT NAME

You might also like