Search
K
< Back

Retrieve Data

Retrieving external patient records through Patient360 enriches internal systems with a complete, normalized clinical history aggregated from connected networks. Retrieval runs as an asynchronous process that assembles, normalizes, and deduplicates clinical data into a unified FHIR record bundle used across clinical and operational workflows.

Use Cases

Record retrieval can be triggered at any stage in which external clinical data is required. Common examples include:

  • Patient intake or registration
  • Chart review prior to scheduled encounters
  • Care coordination and transitions of care
  • Population-health, quality, and risk-adjustment programs
  • Referral management and network event follow-up

Retrieval frequency and timing depend on the system’s performance expectations and program objectives.

Process Overview

A standard Patient360 retrieval request follows the sequence below:

  1. Patient discovery and auto-enrollment across connected networks
  2. Document queries issued to locate available clinical data
  3. Ingestion and processing of structured and unstructured records
  4. Normalization, terminology mapping, and deduplication
  5. Assembly of normalized resources into a unified Patient360 FHIR Bundle
  6. Delivery of results to your configured webhook endpoint (or polling if enabled)

Patient360 orchestrates the full end-to-end workflow; separate discovery, enrollment, and document-query steps are not required.

Initiating Retrieval

Record retrieval is initiated using the $p360-retrieve operation and executes asynchronously.

  • A retrieval job is created when the request is submitted
  • Result notifications are delivered to a webhook endpoint
  • Polling is available but not recommended as a primary mechanism
  • Subscriptions can be configured to notify your system as new records become available

Optional retrieval-scope filtering allows inclusion or exclusion of resource types.

Output Format

Retrieval returns a FHIR Bundle containing:

  • Standard resources such as Patient, Encounter, Observation, Condition, Procedure, MedicationStatement, and DocumentReference
  • Normalized and mapped terminology values (LOINC, SNOMED CT, RxNorm)
  • References to unstructured documents (C-CDA, imaging reports)
  • Metadata describing source system provenance and matching confidence

Network Sources

Patient360 retrieves records from:

  • Carequality-connected EHRs and health systems
  • CommonWell participants
  • eHealth Exchange (eHX)
  • Regional lab and radiology networks
  • TEFCA exchanges (if enabled)

Routing behavior is based on demographics, enrollment status, and network participation.

Key Benefits

Patient360 retrieval enables organizations to:

  • Enrich internal records with comprehensive external clinical history
  • Improve clinical decision-making and care coordination
  • Support population-health and risk-adjustment programs
  • Reduce manual record gathering and reconciliation efforts

Patient360 ensures that complete external records are available when needed to support clinical, operational, and analytical workflows.