Providing patient financial data to Hopkins staff

If you are experiencing problems accessing the DataMart Site please see our FAQ Section for assistance.

Table of Contents

I.   DataMart Mission Statement

II.  DataMart History & Background

III. DataMart Data Overview 

IV. CCUB Documenter

I. DataMart Mission Statement

• Providing patient financial data to Hopkins staff.

II. DataMart History & Background

• The 1995 Johns Hopkins Integrated Financial Information Systems (IFIS) study and the 1996 Reengineering project indicated that data is often buried in operational systems with no effective way to query it or combine data from multiple sources.
• In Autumn 1996, staff from the JHH Casemix Information Management Department, JHM Center for Information Services, JHHS Planning and Marketing Division, and Bayview Medical Center began the development of data repositories at Johns Hopkins.
• JHH Casemix Information Management developed the JHM DataMart using Microsoft SQL Server database software. It contains JHH Casemix and billing, Bayview Casemix and billing, and Maryland HSCRC discharge and ambulatory surgery data.
• The "Client-Server" configuration of the DataMart consists of a server running Microsoft SQL Server software as the "back-end" data storage application, and a variety of PC workstation SQL-Compliant applications as the "front-end" used to query that data. Microsoft Access has been selected as the front-end application that will be supported by Casemix Information Management.
• Using the DataMart requires a desktop computer connected to the JHMI local area network with a SQL-compliant application such as Microsoft Access. A DataMart user account is also needed.
• In order to make querying data easier for non-Access users, CIMD has developed "point and click" query tools named CView (for the JHH Casemix data) and HView (for the Maryland HSCRC data).

III. DataMart Data Overview

• Patient Health Data - Up to 15 ICD9 diagnosis codes, Up to 15 ICD9 procedure codes, Diagnosis Related Group (DRG), Birth weight.
• Patient Demographic Data - Age, Sex, Race, Marital Status, Zip Code, Hospital Charges (Total, Routine, Operating Room, Pharmacy, Radiology, Laboratory, Supplies, Therapies, Other), Lengths of Stay (Total, ICU/SICU, CCU, NICU, PICU) .
• Admission & Discharge Data - Nature of admission (Delivery, emergency, urgent, elective, etc.), Source of admission (Home, transfer, outpatient surgery, etc.), Emergency room admission.
• Discharge disposition - Home, died, hospital, nursing facility, etc.
• Payment Sources - Broad categories in HSCRC, insurance company in Casemix.
• Health Care Provider Data - Discharging Hospital, physician, nursing unit; Operating Physician.
• Billing Detail Data - includes charges and quantity for each billed item by service date.
• Readmission data
• Insurance denial data
• Pharmacy billing detail

 IV. CCUB Documenter

• The purpose of CCUB Reason Documenter is to:
  • Obtain a list of patient accounts in the CCUB data that have not been billed and do not have sufficient documentation for billing to proceed.
  • Document a reason for individual accounts re: why the required info can not be provided.