Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
CarePath
Healthcare
Care coordination for provider networks: referral intake, triage, scheduling and follow-up with clinician oversight.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v1
Problem
Referrals are faxed, emailed and re-keyed; patients fall through the gaps and nobody sees where a referral is stuck.
Outcome
Referrals are visible end-to-end, triaged consistently and closed with follow-up.
Who uses it
- Clinician
- Operations Analyst
Key capabilities
Referral intake
IncludedStructured referral forms and document capture.
Domain:
referralsUrgency triage suggestions
AI-assistedIncludedSuggest urgency from referral content for clinician approval.
Scheduling
IncludedBook appointments against capacity.
Domain:
schedulingFollow-up tracking
IncludedTrack outcomes and close the loop with the referrer.
Typical workflow
Referral to appointment
Trigger: A referral is received
Task
Stage 1: Capture referral
Coordinator
AI-assisted
Stage 2: Suggest urgency
System
Human checkpoint
Stage 3: Clinician triage
Clinician
Task
Stage 4: Schedule appointment
Coordinator
Automated
Stage 5: Notify referrer
System
Task Automated AI-assisted Human checkpoint Decision
About this foundation
CarePath coordinates patient referrals across departments and partner providers. Referrals are captured with structured clinical context, triaged by urgency with AI assistance, scheduled, and followed up until closure. Clinicians approve every triage decision.
Related applications
- • Addresses the same problem: Fragmented Systems, Manual Workflow
- • Shared capabilities: Workflow Automation
- • Addresses the same problem: Fragmented Systems, Manual Workflow
- • Shared capabilities: Workflow Automation
- • Addresses the same problem: Fragmented Systems, Manual Workflow
- • Shared capabilities: Workflow Automation
- • Addresses the same problem: Fragmented Systems, Manual Workflow
- • Shared capabilities: Workflow Automation
- • Addresses the same problem: Fragmented Systems, Manual Workflow
- • Shared capabilities: Workflow Automation
- • Addresses the same problem: Fragmented Systems, Manual Workflow
- • Shared capabilities: Workflow Automation
Referral to appointment
Trigger: A referral is received
Task
Stage 1: Capture referral
Coordinator
AI-assisted
Stage 2: Suggest urgency
System
Human checkpoint
Stage 3: Clinician triage
Clinician
Task
Stage 4: Schedule appointment
Coordinator
Automated
Stage 5: Notify referrer
System
Actors
Referrer, Coordinator, Clinician
Outputs
- Scheduled appointment
- Referral status
Evidence generated
- Triage decision record
Exceptions
- Incomplete referral returned to referrer
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Referral intake
IncludedStructured referral forms and document capture.
Domain:
referralsUrgency triage suggestions
AI-assistedIncludedSuggest urgency from referral content for clinician approval.
Scheduling
IncludedBook appointments against capacity.
Domain:
schedulingFollow-up tracking
IncludedTrack outcomes and close the loop with the referrer.
HL7 FHIR exchange
ExtensionFHIR-based exchange with EHRs.
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 6
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- 6 bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- referrals
- patients
- triage
- scheduling
- followups
- identity
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
Data
| Integration | Status | Direction | Method |
|---|---|---|---|
| EHR (HL7 FHIR) | Customer-Specific | bidirectional | FHIR |
Identity
| Integration | Status | Direction | Method |
|---|---|---|---|
| Microsoft Entra ID | Reference Adapter | bidirectional | OIDC |
Communication
| Integration | Status | Direction | Method |
|---|---|---|---|
| SMS notifications | Standard API Pattern | outbound | REST |
Deployment
- Deployment models
- Private Cloud, Customer VPC/VNet
- Cloud profiles
- Azure Profile, AWS Profile
- Containerized
- Yes
- Regions
- UAE, SAUDI ARABIA
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Yes
- Data leaves customer environment
- No
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Yes
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 1
- Last published
- 23 Sept 2026