Continuity across entities
Teams coordinate care within defined entity, patient-record and access boundaries.
Medical Cities
Your medical city. Connected with control.
Connect care across entities, departments and revenue while keeping record boundaries and access accountable.
27Capabilities in the starting scope
4Workflow case studies
360° SOLUTION COVERAGE
Network governance
Define entities, record boundaries and accountable access across the agreed network.
MANSOQ IN PRACTICE
See the whole journey at work.
Four complete operational cases. Read each one here.
END-TO-END WORKFLOW CASE
Continuity across entities
Teams coordinate care within defined entity, patient-record and access boundaries.
The situation
A patient moves between services in a medical-city network. The receiving entity needs the permitted care context while each organization retains its data boundaries.
What MANSOQ connects
Continuity across entities requires governed access, not unrestricted record sharing.
The people involvedIntegration & IT teamTreating clinicianAccess & coordinationService leadership
The complete journey
Define the network boundary
Integration & IT teamAgree the entities, identity scope and permitted record exchange for this composition.
Entities · Identity boundary · PermissionsRecord the source encounter
Treating clinicianDocument the patient’s current encounter and reason for the next service.
Source encounter · Referral reasonCoordinate the receiving service
Access & coordinationConfirm the destination and responsible team for the referral or transfer.
Destination · Team · TransferShare the permitted context
Integration & IT teamCarry the agreed information through the selected connection with source references.
Interface · Source record · Shared contextDocument receiving care
Treating clinicianReview permitted information and document the receiving entity’s encounter and responsibilities.
Receiving encounter · Care planReview continuity with governance
Service leadershipReview supported network reporting within the agreed entity and access boundaries.
Entity view · Access · Reporting
The factors that make it work
Starting information
Entities · Identity boundary · Permissions
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
Identity or access cannot be confirmed
If an identity cannot be matched or access is outside the agreed boundary, the responsible teams resolve it before exchanging additional records.
Responsible team · Integration & IT teamAn identity or access mismatch
Resolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamAn unavailable source or connection
Use the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Network GovernanceNative operation · Agreed connectionConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Emergency into inpatient care
The admitting team receives the documented emergency encounter and care responsibilities.
The situation
A medical-city outpatient service refers a patient for admission. The referral, receiving ward and financial encounter need connected responsibilities.
What MANSOQ connects
Changing the care setting should not remove the reason the patient arrived.
The people involvedTreating clinicianAccess & coordinationNursing teamFinance teamIntegration & IT team
The complete journey
Document the referral
Treating clinicianRecord the outpatient assessment and documented admission referral.
Outpatient encounter · ReferralConfirm the receiving entity
Access & coordinationEstablish the destination service and the patient identity within the agreed network boundaries.
Destination · Identity · EntityCreate the admitted encounter
Access & coordinationConnect the admission and ward responsibility to the receiving entity’s record.
Admission · Ward · EncounterReview the handover context
Nursing teamReview available referral notes and record the receiving ward’s observations and responsibilities.
Referral notes · Ward handoverCoordinate care and departments
Treating clinicianDocument inpatient care and connect required department requests to the admitted encounter.
Care plan · Orders · ResultsComplete care and financial follow-up
Finance teamRetain the discharge context and review each entity’s recorded charges and account responsibility.
Discharge · Entity charges · Account
The factors that make it work
Starting information
Outpatient encounter · Referral
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
The destination changes
When the destination changes, update the responsible entity and transfer record; cross-entity sharing still follows the agreed permissions.
Responsible team · Access & coordinationAn identity or access mismatch
Resolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamAn unavailable source or connection
Use the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Emergency CareNative operationConfirm deployment scope
Inpatient CareNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Network GovernanceNative operation · Agreed connectionConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
Patient AccessNative operationConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Diagnostics and medication across teams
Specialist departments connect orders, available results and dispensing to the care record.
The situation
Several medical-city departments contribute to a patient’s care. The network needs to distinguish native operation from information exchanged with existing systems.
What MANSOQ connects
Connected results and operating a department are different responsibilities.
The people involvedService leadershipTreating clinicianDepartment teamIntegration & IT teamRevenue team
The complete journey
Define departmental ownership
Service leadershipAgree which departments operate in MANSOQ and which retain an external system.
Department · Operating mode · OwnerCreate the encounter request
Treating clinicianLink each requested service to the correct patient, encounter and department.
Order · Encounter · DepartmentPerform the selected department work
Department teamDocument supported native activity or process the request in the retained source system.
Department activity · Source referenceReturn the agreed information
Integration & IT teamExchange the agreed results or status through the defined interface and identity mapping.
Result · Interface · Identity mappingReview in the care context
Treating clinicianReview available department information and document the next care responsibility.
Clinical review · Next actionTrace the service account
Revenue teamReview selected charge linkage with the service’s native or external source reference.
Service · Charge · Source
The factors that make it work
Starting information
Department · Operating mode · Owner
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
The department interface fails
If an interface fails, the agreed operational fallback and source owner handle the missing information; connected access does not replace departmental operation.
Responsible team · Integration & IT teamAn identity or access mismatch
Resolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamAn unavailable source or connection
Use the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
LaboratoryNative operationConfirm deployment scope
PharmacyNative operationConfirm deployment scope
InventoryNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Network GovernanceNative operation · Agreed connectionConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
A leadership view grounded in source data
Leadership reviews selected operational and revenue reporting within governed boundaries.
The situation
Medical-city leaders review operational and revenue activity across selected entities. They need comparable views with a clear source and reporting boundary.
What MANSOQ connects
A network report is useful only when the included entities and definitions are clear.
The people involvedService leadershipDepartment teamRevenue teamIntegration & IT team
The complete journey
Agree the reporting view
Service leadershipDefine the operational question, selected entities and authorized audience.
Question · Entities · AccessIdentify the source activity
Department teamRecord the relevant care and departmental activity within its source entity.
Activity · Entity · EncounterConnect revenue context
Revenue teamReview claims, financial responses and outstanding work within the selected reporting scope.
Claims · Responses · Work itemsReview the reporting boundaries
Integration & IT teamCheck included sources, entity permissions and the agreed operational definitions.
Sources · Permissions · DefinitionsReview the selected report
Service leadershipUse supported operational and revenue views to identify work requiring attention.
Report · Review · Work requiring actionAssign accountable follow-up
Service leadershipRecord the responsible team and return operational questions to the relevant source.
Action · Owner · Source reference
The factors that make it work
Starting information
Question · Entities · Access
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
A reporting source is incomplete
An incomplete source is identified in the review rather than silently treated as zero activity; the source owner resolves the reporting gap.
Responsible team · Service leadershipAn identity or access mismatch
Resolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamAn unavailable source or connection
Use the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Advanced AnalyticsNative operationConfirm deployment scope
Network GovernanceNative operation · Agreed connectionConfirm deployment scope
RCM ReportingNative operation · Agreed connectionConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
Make it your medical city.
Your solution is already selected. Adjust the services and review your proposal.