Device data infrastructure for ACCESS Model teams

ROOK Connect unifies wearables and home-health devices into normalized data, so CMS ACCESS Model teams can report outcomes across every condition from one integration.

The problem, solved

ROOK is the connective tissue for ACCESS device data.

ACCESS asks programs to track outcomes across several conditions. Flip the switch to see what changes with ROOK.

ACCESS
  • Fragmented device integrationsEvery wearable and every meter brings its own SDK, quirks and outages.
    One API, many devicesA single integration reaches the wearables and home-health devices your participants use.
  • Non-standardized dataBlood pressure, glucose, weight and activity arrive in incompatible shapes.
    Normalized dataBlood pressure, glucose, weight, activity and sleep delivered in one consistent schema.
  • Reporting is a bottleneckAnalysts spend more time cleaning data than surfacing outcomes.
    Structured outputsStructured data that plugs into your workflows, dashboards and reporting.

New add-on · Clinical Ready

Turn normalized health data into FHIR R4 documents.

ACCESS reporting needs interoperable clinical data. The Clinical Ready add-on turns your users' normalized summaries into FHIR R4 bundles your EHR can consume.

  • FHIR R4 documentsNormalized health summaries are transformed into FHIR R4 documents, ready for EHR/EMR ingestion.
  • LOINC codes and UCUM unitsEvery observation arrives annotated with standard clinical codes and units, with no mapping work on your side.
  • No additional integrationEach time a summary is generated or updated, ROOK delivers a FHIR Bundle through your existing Data Webhook.
Read about add-ons

Illustrative example of the FHIR R4 output.

FHIR R4 BundleObservation · JSON
{  "resourceType": "Bundle",  "type": "collection",  "entry": [{ "resource": {    "resourceType": "Observation",    "status": "final",    "code": { "coding": [{      "system": "http://loinc.org",      "code": "85354-9",      "display": "Blood pressure panel"    }] },    "component": [      { "code": "8480-6", "valueQuantity": { "value": 128, "unit": "mm[Hg]" } },      { "code": "8462-4", "valueQuantity": { "value": 82, "unit": "mm[Hg]" } }    ]  } }]}
FHIR R4 BundleObservation · JSON
{  "resourceType": "Bundle",  "type": "collection",  "entry": [{ "resource": {    "resourceType": "Observation",    "status": "final",    "code": { "coding": [{      "system": "http://loinc.org",      "code": "2339-0",      "display": "Glucose [Mass/volume] in Blood"    }] },    "valueQuantity": {      "value": 104,      "unit": "mg/dL",      "system": "http://unitsofmeasure.org"    }  } }]}

Use cases

Built for the conditions ACCESS tracks.

  • CKM / ECKM

    Chronic condition management

    • Blood pressure
    • Glucose
    • Weight
  • MSK

    Musculoskeletal care

    • Mobility
    • Steps and activity
    • Recovery
  • Behavioral health

    Whole-person insights

    • Sleep quality
    • Behavioral signals
    • HRV

ACCESS readiness

The five capabilities an ACCESS-ready program needs.

Each one is a common gap in device programs. Here is the part of ROOK that covers it.

  1. Multi-device ingestionData from every wearable and home-health device your participants use.ROOK Connect
  2. Continuous data collectionReadings that keep arriving between visits, not only at them.APIs and mobile SDKs
  3. Structured outcomesData your analysts can report on without cleaning it first.Normalized data structures
  4. Interoperability (FHIR)Observations your EHR/EMR can ingest as FHIR R4.Clinical Ready add-on
  5. Scalable data pipelineIngestion, normalization and delivery that hold up as your program grows.Webhooks and API delivery

5/ 5

ROOK covers all five, with FHIR R4 through the Clinical Ready add-on.

See it in a walkthrough

ACCESS Model

Get your program ready for ACCESS.

Book a walkthrough and see how teams unify device data into reportable outcomes with ROOK.

FAQ

Frequently asked questions about ROOK for the ACCESS Model

How ROOK unifies, normalizes and delivers device data for ACCESS programs.

What does ROOK provide for ACCESS Model programs?

ROOK Connect unifies wearables and home-health devices into normalized data, so ACCESS Model teams can report outcomes across every condition from one integration.

Which data does ROOK normalize for ACCESS reporting?

Blood pressure, glucose, weight, activity and sleep are delivered in one consistent schema, as structured data that plugs into your workflows, dashboards and reporting.

How does ROOK deliver FHIR R4 data?

The Clinical Ready add-on transforms normalized health summaries into FHIR R4 documents annotated with LOINC codes and UCUM units. Each time a summary is generated or updated, ROOK delivers a FHIR Bundle through your existing Data Webhook, with no additional integration.

Which conditions does ROOK support for ACCESS?

ROOK supports the conditions ACCESS tracks, including chronic condition management (CKM / ECKM), musculoskeletal care (MSK) and behavioral health.

Which ACCESS readiness capabilities does ROOK cover?

ROOK covers all five: multi-device ingestion through ROOK Connect, continuous data collection through APIs and mobile SDKs, structured outcomes through normalized data structures, FHIR interoperability through the Clinical Ready add-on, and a scalable pipeline through webhooks and API delivery.

Still have questions?Our team can review your sources and use case with you.
Schedule a demo

Newsletter

Stay in the loop.

Sign up with your email address to receive news and updates from the ROOK team.

We respect your privacy. Read our privacy policy.