Dev:LH MOC Admin-MOC: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 55: | Line 55: | ||
•Support operational governance and compliance | •Support operational governance and compliance | ||
== '''Medical Operation Centers Overview Screen''' == | |||
'''Medical Operation Centers Overview Screen''' | |||
This screen provides a centralized view of all configured Medical Operation Centers. | This screen provides a centralized view of all configured Medical Operation Centers. | ||
| Line 98: | Line 96: | ||
Centers can be removed if no operational dependencies exist. | Centers can be removed if no operational dependencies exist. | ||
(Deletion should be restricted if the center is currently active or has authoritative operational responsibility.) | (Deletion should be restricted if the center is currently active or has authoritative operational responsibility.)[[File:MOC overview.png|none|thumb]] | ||
== '''Medical Operation Center Detail Screen''' == | |||
This screen allows administrators to configure a specific Medical Operation Center. | This screen allows administrators to configure a specific Medical Operation Center. | ||
| Line 160: | Line 156: | ||
•A clear error message is displayed if connection attempts fail. | •A clear error message is displayed if connection attempts fail. | ||
•The status indicator updates automatically. | •The status indicator updates automatically.[[File:MOC details.png|none|thumb]] | ||
[[File:MOC details.png|none|thumb]] | |||
== Related articles == | == Related articles == | ||
[[Dev:LH Core Admin-MOC Translations|Translations]] | [[Dev:LH Core Admin-MOC Translations|Translations]] | ||
Latest revision as of 10:41, 18 February 2026
The Medical Operation Centers (MOC) administration application allows system administrators to manage the operational centers responsible for processing Special Assistance Requests (SARs).
Medical Operation Centers are the core operational units that:
•Review medical information
•Perform fit-to-fly assessments
•Coordinate special services (e.g., STCR, WENOLL, Ambulance)
•Orchestrate delivery partners
•Oversee operational and compliance workflows
This module ensures that the system always reflects the correct operational landscape.
Why This Module Is Important
Medical Operation Centers are the operational heart of the SAR process.
Keeping this module accurate ensures:
•Correct medical case routing
•Proper approval workflows
•Reliable digital communication
•Controlled operational governance
•Compliance with medical and aviation regulations
Without accurate MOC configuration:
•Requests may be misrouted
•Digital workflows may fail
•Operational accountability may be unclear
Purpose
The purpose of this module is to:
•Maintain an up-to-date directory of Medical Operation Centers
•Control which centers are digitally connected
•Ensure correct routing of cases
•Enable smooth collaboration via B-Op digital integration
•Support operational governance and compliance
Medical Operation Centers Overview Screen
This screen provides a centralized view of all configured Medical Operation Centers.
What Users Can See
A table listing all MOCs, including:
Column Description
Center Name Official name of the Medical Operation Center
Logo Visual identifier (if uploaded)
B-Op Connection Status Shows if digital connection is active
Connection Indicator Visual status (Connected / Not Connected)
Functional Capabilities
View Medical Operation Centers
Administrators can see all existing centers in a structured table format.
🔍 Search
A search field allows filtering centers by name.
➕Add New Center
A clearly visible “Add New” button allows administrators to create a new Medical Operation Center entry.
✏️ Edit Existing Center
Each center can be opened and edited.
❌Delete Center
Centers can be removed if no operational dependencies exist.
(Deletion should be restricted if the center is currently active or has authoritative operational responsibility.)

Medical Operation Center Detail Screen
This screen allows administrators to configure a specific Medical Operation Center.
General Information
Administrators can define:
Field Description
Center Name Official name of the MOC
Upload Logo Optional visual identity for easy recognition
The logo helps users quickly identify the responsible center within workflows and dashboards.
Digital Connection (B-Op Integration)
The Digital Connection section manages integration with the B-Op ecosystem.
This determines whether the Medical Operation Center can:
•Receive digital case assignments
•Exchange messages securely
•Send and receive structured data
•Synchronize operational status
B-Op Digital Connection Status
The system clearly shows:
•✅ Connected (green indicator)
•❌ Not Connected (red indicator)
This provides immediate operational visibility.
Available Actions
Connect
If a center is not connected, administrators can initiate a digital connection.
Re-Check
If already connected, administrators can re-validate the connection status.
Confirmation & Error Handling
•A confirmation message is shown when the connection is successfully established.
•A clear error message is displayed if connection attempts fail.
•The status indicator updates automatically.
