Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
10 views6 pages

Class Note

The document outlines the functional requirements and application stack design for a healthcare management system, detailing various microjourneys such as patient registration, medical help services, and patient admission processes. It includes case design for different services like therapy requests and ambulance requests, along with a comprehensive data model for managing patient information, medical history, and appointments. Additionally, it discusses potential application architecture options and lists the build machines involved in the project.

Uploaded by

lagosom203
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views6 pages

Class Note

The document outlines the functional requirements and application stack design for a healthcare management system, detailing various microjourneys such as patient registration, medical help services, and patient admission processes. It includes case design for different services like therapy requests and ambulance requests, along with a comprehensive data model for managing patient information, medical history, and appointments. Additionally, it discusses potential application architecture options and lists the build machines involved in the project.

Uploaded by

lagosom203
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 6

Pega CLSA 24: Weekday Batch: Jun 16th, 2025

----------------------------------------------------------

---------------------------------------HCMS-------------------------------------

Functional Requirement:

Microjourney:

Patient Registration
Medical Help Services
--Ambulance Services: MHS
Medical Camp
Appointment
Patient Admission:
--Invoice Generation: Not a MJ
Patient Death:
--Discharge Process: Admission
--Therapy Request and Billing: MHS
--Surgery Process : Admisison
--MR Appointment : Its a part of Appointment
--Room Reservation: Not a MJ
--Approval- PRO: Not a MJ
--Medical Insurance Check: Not a MJ

Patient Registration: Case Instance First

1. Patient Registration: Case Type --- Selected

2. Flow in a Comp App/Org App


3. Landing Page with CRUD Operation
4. Temporary Case

Medical Help Services: Case Instance First (Tow independant case types)

1. Therapy Request
2. Ambulance Request

Medical Camp: Divide and Conquor

1 Camp
1.1 Patient/MC Patient/Visitor

Appointment:Case Instance First (Tow independant case types)


Patient Appointment
MR Appointment

Patient Admission

EAS Admission
Admisison
Surgery
Death
Death

Application Stack Design ( Situational Layer Cake)

Option 1: One Enterprise, 3 production application (built on Enterprise)


Option 2: 3 production application
Option 3: Framework, 3 production application (built on Framework)

Case Design

Patient Registration

Intake Resolve
Patient Details (when source!=API) Save Patient Info
Enter Patient Details Save The Patient
Data

Dupe Check
go to Duplicate

Duplicate (Resolved-Duplicate)

Therapy Request

Intake Resolve
Capture Request Generate Invoice
Enter Patient
Select Therapy

Ambulance Request

Intake Resolve
Capture Request Create EAS Admission
Enter Patient
Enter Request Detail

Patient Appointment

Intake Appointment Consultation


Resolve

Patient Selection Appointment Booking Patient


Consultation
Select Patient Book Appointment Enter
Consultation Log

Patient Registration Admission (Resolve-Admitted)


Enter Patient Details Collect Patient Consent
Go to Appointment Create Admission (If advised)

MR Appointment
Intake Appointment Approval
Consultation Resolve
Eter MR Detail Appointment Booking FLO Approval
MR Discussion
Book Appointment
Enter Discussion Log

Rejection
Notify MR

Medical Camp Appointment In Camp


Resolve

Intake Book Appointment Enter


Patient Summary
Initiate Camp Select Doctors and date Add Camp
Patient (Local Action)
Enter Camp Details

Camp Patient

Intake Book Appointment Consultation


Resolve
Enter Patient Select Doctor Enter Consultation
Log (List) Create admission (If advised)

Patient Registration

Enter Patient Details


Go to Appointment

EAS Admission

Intake (Skip if API) Treatment Resolve


Enter Patient ID Complete Treatment
Enter Treatment Log(Local Action)

Admission Death
Create Admission Create Death

Admission

Intake Admission
Discharge Resolve

Enter Preferences Complete Treatment (cant not complete until child


cases are resolved) Generate Invoice
Enter Treatment Log(Local Action)
Confirm payment
Initiate Surgery(Local Action, if recom)
If death, go to Death
Force Discharge (Local Action)
Death Force Discharge
Create Death PRO Approve (if rejected, go to admission)
Discharge (Process)

Surgery
Intake Approval Resource Booking
Surgery Resolve
Select Surgery PRO Approval Book rooms, nurses,
doctors Complete Surgery Update Admission

Enter Treatment Log(Local Action)


Death

Create (Skip) Gov Exec Approval PRO Approval


Resolve

Confirm Body Handover

Data Model:

1. List down all possible data models


Patient -----------
Departments : Doctors
Rooms
Surgery
Therepay
Insurance
OT
Nurse
Medical History/Treatment Log
Death
Appointment
Ambulance Requst
Camp
Doctor
MR----------- Data-Party-Person (PegaData-Contact)
Medication---
Discharge
Invoice
Payment

2. Refine/finalize Data Model

FLL-Data-Patient (PegaData-Contact): Abstract


ID
MedicalHistory (List: )
Insurance (Page: FLL-Data-Insurance)
Address (Page: Address)

FLL-Data-Insurance: Abstract
Patient ID
Provider
Policy Name
Policy ID
Limit
Start Date
End Date
Coverage (Text Area)
FLL-Data-MedicalHistory:Abstract
Patient ID
Case ID
Start Date
End Date
Type (Therapy/Surgery/Allergy/Illness/AmbulanceRequest)
Note
Hospital
Doctor
FLL-Data-Address (PegaData-Address):Abstract
Patient ID
FLL-Data-Employee(PegaData-Contact)

FLL-Data-Employee-Doctor: Concrete: CustomerData


pyGUID (Key)
Department
DeptID
ID
Name
Specialization
Experience (In years)
Rating
Registration/Licence ID
FLL-Data-Service: Abstract
Type
Cost
Description
Category
ID
FLL-Data-Service-Room:Concrete: CustomerData (Key: Type)
Add. Cost
Features
FLL-Data-Service-Surgery:Concrete: CustomerData
Type (Key)

FLL-Data-Service-Therepy:Concrete: CustomerData
ID (Key)

FLL-Data-Service-OT:Concrete: CustomerData
ID (Key)

FLL-Data-Employee-Nurse:Concrete: CustomerData
ID (Key)
pyName

FLL-APMS-Data-Appointment: Concrete: CustomerData


pyGUID (Key)
ID
Date and Time
Subject ID
Doctor
Department
Type(MR/Patient/MC)

FLL-PRMS-Data-EAR : Absract
Patient ID
Date and Time
Address(Page:PegaData-Address)
Remark
FLL-APMS-Data-Camp: Abstract
ID
pyName
Date
Venue (Page:PegaData-Address)
Doctors (List:FLL-Data-Doctor)

Invoice

FLL-IPMS-Data-Admission: Abstract
Type
Patient ID
Admission Date
Discharge Date
Remark
Room(Page:FLL-Data-Service-Room)
Food Preferences
Daily Log (List: FLL-Data-MedicalHistory)

FLL-PRMS-Data-Patient (FLL-Data-Patient): Concrete: CustomerData


ID (Key)
FLL-PRMS-Data-Insurance (FLL-Data-Insurance): Concrete: CustomerData
Patient ID(Key)
FLL-PRMS-Data-MedicalHistory (FLL-Data-MedicalHistory):Concrete: CustomerData
pyGUID (Key)
FLL-PRMS-Data-Address (FLL-Data-Address):Concrete: CustomerData
Patient ID (Key)

Build Machines:

Arya
Sumit
Kesav
Prabhat

You might also like