Synthetic data prototype — no PHI. Numbers, names, and IDs are fabricated for design review only.

Integration

Data Source & FHIR R4 Mapping

System-of-record provenance and FHIR resource mapping powering this pilot.

EHR FHIR R4

6 domains · avg 81%

Discharge Metadata
Encounter
93%
Follow-up Scheduling
Appointment
76%
Utilization Outcomes
Encounter
56%
Medication Reconciliation
MedicationRequest
73%
Procedure Metadata
Procedure
94%
Demographics
Patient
93%

Arkos PROM API

2 domains · avg 55%

Satisfaction
QuestionnaireResp.
53%
PROMs
Observation
57%

SPOC-CO Workflow

6 domains · avg 67%

TCM Documentation
ServiceRequest
77%
Steerage History
ServiceRequest
57%
PCM Monthly Activity
CarePlan
51%
Referral Intake
ServiceRequest
83%
Pre-Visit Workup
ServiceRequest
69%
Pre-Visit Readiness
CarePlan
65%

Pipeline Architecture

EHR FHIR R4

Source of truth

SPOC-CO Ingest

Validation & normalization

Episode Engine

TCM/PCM workflows

Arkos RWE Lake

Analytics & evidence

Billing 837P

Claim submission

74 synthetic patients · 442 RWE completeness rows ingested.

Sample FHIR Resource — CarePlan (PCM)

{
  "resourceType": "CarePlan",
  "status": "active",
  "intent": "plan",
  "category": [{ "coding": [{ "system": "http://snomed.info/sct", "code": "734163000", "display": "Care plan" }]}],
  "subject": { "reference": "Patient/PT-000001" },
  "period": { "start": "2026-02-14" },
  "author": { "reference": "Practitioner/STF-005" },
  "addresses": [{ "reference": "Condition/post-op-urology" }],
  "activity": [{
    "detail": {
      "code": { "coding": [{ "system": "http://www.ama-assn.org/go/cpt", "code": "99426" }]},
      "status": "in-progress",
      "scheduledTiming": { "repeat": { "frequency": 1, "period": 1, "periodUnit": "mo" }}
    }
  }]
}

EPIC Workflow Layer

EPIC Workflow Mapping (synthetic prototype)

Future-state mapping of intake, AI activation, pathways, order sets, tasks, and program enrollment against EHR / ADT / FHIR / SPOC / RCM sources.

This prototype uses synthetic data only. Live Cerner, ADT, FHIR, device, pharmacy, post-acute, and RCM integrations remain future implementation tracks.

EHR / ADT candidate fields

candidate fields

SPOC operational fields

candidate fields

AI / routing fields

candidate fields

Task orchestration fields

candidate fields

Billing / RCM fields

candidate fields

Synthetic demo-only fields

candidate fields

Source Ownership

USC / EHR

2 fields

AI Activation Engine

1 field

SPOC / Arkos

5 fields

Billing / RCM

1 field

Operations

3 fields

Workflow-Specific Mapping Rows

Synthetic mapping of EPIC workflow model fields to candidate source systems and FHIR resources.

Field	Description	Mapping Category	Owner	FHIR Candidate
fact_intake_trigger.care_trigger_type	Inbound signal class (ADT, surgery schedule, panel upload, referral)	ADT / HL7 Candidate	USC / EHR	Encounter.class / MessageHeader.event
fact_intake_trigger.care_trigger_source	Originating system that produced the intake event	Cerner / EHR Candidate	USC / EHR	MessageHeader.source.endpoint
fact_intake_trigger.ai_activation_score	AI-derived likelihood-to-benefit score for routing	SPOC Operational Layer	AI Activation Engine	RiskAssessment.prediction.qualitativeRisk
fact_program_assignment.recommended_program	Recommended program (TCM, PCM, APCM, RPM, IPC, DME)	SPOC Operational Layer	SPOC / Arkos	CarePlan.category
fact_program_assignment.eligibility_status	Coverage / payer eligibility for assigned program	Rev-Cycle Validation Required	Billing / RCM	Coverage.status
dim_care_pathway.pathway_name	Standardized clinical pathway driving the order set	FHIR Transform Candidate	SPOC / Arkos	PlanDefinition.title
dim_order_set.order_set_name	Library order set linked to pathway	FHIR Transform Candidate	SPOC / Arkos	ActivityDefinition.title
fact_order_set_activation.orders_generated_count	Count of orders triggered by activation event	SPOC Operational Layer	Operations	ServiceRequest (n)
fact_workflow_task.task_type	Generated task class (outreach, consent, education, billing prep)	SPOC Operational Layer	Operations	Task.code
fact_workflow_task.required_license_level	Minimum license required to action the task	SPOC Operational Layer	Operations	Task.performerType
fact_care_plan_instance.program	Active program enrollment per patient	SPOC Operational Layer	SPOC / Arkos	CarePlan.category / status
fact_panel_candidate.panel_type	Office-based panel source (PCP roster, specialty roster, referral)	Synthetic Demo Only	SPOC / Arkos	Group.type / Group.member

Referral Center On-Ramp

Referral Center Mapping (synthetic prototype)

Future-state mapping of referral intake, pre-visit workup, and visit-readiness fields against USC Referral Center, OneLine, Cerner, scheduling, billing/RCM, SPOC, and RWE sources.

This prototype uses synthetic data only. Live referral center, OneLine, Cerner, scheduling, and billing integrations remain future implementation tracks.

Referral source fields

candidate fields

OneLine outreach/intake fields

candidate fields

Cerner/scheduling candidate fields

candidate fields

SPOC operational fields

candidate fields

RWE fields

candidate fields

Billing/RCM fields

candidate fields

Referral Source Ownership

USC Referral Center

9 fields

Scheduling

2 fields

Analytics

1 field

Cerner / EHR

1 field

SPOC / Arkos

4 fields

OneLine

1 field

Referral Center Mapping Rows

Synthetic mapping of referral intake, workup tracker, and pre-visit readiness fields to candidate source systems and FHIR resources.

Field	Description	Mapping Category	Owner	FHIR Candidate
fact_referral_intake.referral_id	Unique synthetic referral identifier	USC Referral Center	USC Referral Center	ServiceRequest.identifier
fact_referral_intake.referral_datetime	Timestamp the referral entered the on-ramp	USC Referral Center	USC Referral Center	ServiceRequest.authoredOn
fact_referral_intake.referring_provider_id	Source NPI / provider identifier of referring clinician	External PCP / Community Provider	USC Referral Center	ServiceRequest.requester (Practitioner)
fact_referral_intake.referring_org_name	Referring organization or community practice	External PCP / Community Provider	USC Referral Center	ServiceRequest.requester.onBehalfOf
fact_referral_intake.referral_reason	Free-text reason / chief complaint driving the referral	USC Referral Center	USC Referral Center	ServiceRequest.reasonCode
fact_referral_intake.specialty_requested	Requested specialty (urology, oncology, etc.)	USC Referral Center	USC Referral Center	ServiceRequest.performerType
fact_referral_intake.urgency_level	Urgency classification (routine, urgent, stat)	USC Referral Center	USC Referral Center	ServiceRequest.priority
fact_referral_intake.intake_channel	Channel of receipt (fax, portal, call center, EHR)	Fax / RightFax Candidate	USC Referral Center	ServiceRequest.extension[intake-channel]
fact_referral_intake.documents_received_flag	Whether referring documents have been received	Portal Candidate	USC Referral Center	DocumentReference.status
fact_referral_intake.scheduled_flag	Whether a specialist appointment has been booked	Scheduling Source	Scheduling	Appointment.status
fact_referral_intake.scheduled_date	Date the specialist appointment is scheduled	Scheduling Source	Scheduling	Appointment.start
fact_referral_intake.days_to_appointment	Days from referral receipt to scheduled visit	RWE / Analytics	Analytics	derived (Appointment.start − ServiceRequest.authoredOn)
fact_referral_workup_tracker.workup_type	Pre-visit workup type (imaging, labs, prior auth)	Cerner / EHR Candidate	Cerner / EHR	ServiceRequest.code (LOINC/CPT)
fact_referral_workup_tracker.source_location	Where workup will be performed (USC vs external)	Arkos / SPOC Operational Layer	SPOC / Arkos	ServiceRequest.locationReference
fact_referral_workup_tracker.delay_reason	Reason for workup delay (auth, scheduling, patient)	Arkos / SPOC Operational Layer	SPOC / Arkos	Task.statusReason
fact_pre_visit_readiness.readiness_score	Composite readiness score for the upcoming visit	Arkos / SPOC Operational Layer	SPOC / Arkos	RiskAssessment.prediction.probabilityDecimal
fact_pre_visit_readiness.ready_for_visit_flag	Boolean indicating the patient is visit-ready	Arkos / SPOC Operational Layer	SPOC / Arkos	CarePlan.activity.detail.status (ready)
fact_pre_visit_readiness.missing_items_summary	Outstanding documents / orders blocking readiness	OneLine Intake / Outreach	OneLine	Task.description