Skip to content

[Oracle apex] "ALNoor hospital management" - #605

Merged
aaabAlhosni merged 3 commits into
mainfrom
OracleApex/ALNoor-HospitalManagement
Jul 21, 2026
Merged

[Oracle apex] "ALNoor hospital management" #605
aaabAlhosni merged 3 commits into
mainfrom
OracleApex/ALNoor-HospitalManagement

Conversation

@aaabAlhosni

Copy link
Copy Markdown
Collaborator

A full-featured hospital operations application built with Oracle APEX 26.1,

repo/
├── ALNOOR_SCHEMA.sql # All 13 table definitions — run this first
├── ALNOOR_Full_Data_Load.sql # Sample data: 20+ patients, 10+ doctors, 5+ departments,
│ # 20+ medicines, 30+ appointments, 10+ visits & prescriptions
└── f103.sql # Full Oracle APEX application export (App ID 103, APEX 26.1)

Run the scripts in this exact order using a SQL client (SQL Developer, SQL*Plus, or the APEX SQL Workshop) connected as the schema owner.

Step 1 — Create the schema objects

@ALNOOR_SCHEMA.sql
Step 2 — Load the sample data

@ALNOOR_Full_Data_Load.sql
Step 3 — Import the APEX application

In Oracle APEX:

Go to App Builder → Import
Upload f103.sql
Set the parsing schema to ALNOUR-DB
Click Install Application
The application will be available immediately after import. Log in and navigate to the Home Dashboard to verify the KPI cards populate correctly.
thanks.

@github-actions

Copy link
Copy Markdown

Code Review Comments

  • Title Format: The title should start with a ClickUp ticket ID (e.g. "86ex6r17g: ") instead of “[Oracle apex]” to adhere to the naming convention.

  • Description Accuracy: The pull request description should reflect changes made in the pull request, detailing any specific features or bug fixes introduced, and not just the basic functionality.

  • Indentation Consistency: Ensure all indentation is consistent with the standard of 4 spaces throughout all SQL files.

  • Blank Lines: Check for and remove any unnecessary blank lines throughout the code files to improve clarity and readability.

  • Logic Errors: Review the entire SQL code for logical errors or areas that could benefit from optimization or improvement.

  • Script Execution Order: In the documentation, emphasize the expected order of script execution more clearly.

  • File Comments: Add explanatory comments in each file detailing script purposes, potential side effects, or dependencies on other scripts.

This concise set of comments addresses the necessary adjustments while maintaining relevance to specific lines or sections in the pull request.

New%20session%20-%202026-07-21T12%3A28%3A33.698Z
opencode session  |  github run

@aaabAlhosni
aaabAlhosni merged commit 34097da into main Jul 21, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants