Patient Record Life Cycle Management

• Patient Services Accounting System (PSAS) is currently deployed at
  • Ramakrishna Sevashrama Hospital, Kankhal
  • Ramakrishna Sevashrama Hospital, Vrindaban
  • Ramakrishna Sevashrama Hospital, Delhi

• It manages information about patients visiting the hospital Includes
  • Visits (OPD and IPD Visits)
  • Sub visits (Stay in different Wards, etc.)
  • Services
  • Bill Generation, Payments, and Discharge
• Size of PSAS Database is continuously growing resulting in two major challenges:
  • Overall degradation in performance as size grows
    • Complex Reports (e.g. IPD Dues Report)
    • Bill Generation, etc.
  • May reach the Oracle XE Database Size Limits
• PRLM is developed to address the above challenges.
• In PSAS, the information unit is a patient visit.
• Instead of keeping all patient visits indefinitely
  • Retain Current visit records
  • Archive Recent visit records
  • Purge Very Old visit records

• A Patient visit with visit date before archive point and is still active - visit record is not archived.
  [Reason: Archived records goes into read-only state]
• A Patient visit with visit date before archive point but got discharged after archive pt - visit record is archived.
• Active (Retained) data - Database (can be read or written)
• Archive data - Both the current dump and the archive dump is formed which can be used accordingly (becomes read only; no writes)
• Purged data - Will be deleted (no longer accessible, i.e., no read or write )
  
  

• If Archive point or Purge point only specified: Estimate based on Archive or Purge point
• If both specified: Estimate according to Archive Point.
  
  

 Estimate Tables

• Once the PRLM action is over you can re-examine the DB characteristics of PSAS database to see the database size reduction.

 Currently PRLM has been implemented at Vrindaban and we are getting good speed performance.