Prevent

The Prevent API returns patient-specific recommendations for healthy behavior change

How it works

1

Create a secure identifier

2

Assemble a systems view of your patient's health

3

Generate personalized lifestyle and wellness recs

API specifications

create a unique system_ID for your patient

System does not store any protected health information (PHI) or personally identifiable information (PII) in our data. Read about our security measures.

submit de-identified patient data to generate recs

FHIR-interoperable or customized schemas for patient_biomarkers & _history

• If customized, schemas will be included in user portal.

# Example API Call using the Python requests package

requests.post(
    url=f"{<API_URL>}/{<SYSTEM_ID>}",
    headers={'x-api-key': <API_KEY>},
    data=json.dumps(
    {
      "patient_system_id": <system_id>,
      "patient_biomarkers": sample_biomarker_data,
      "patient_history": sample_questionnaire_data,
      "patient_demographics": sample_demographic_data
    }
  )
)

Data security

To make a patient-specific requests, developers must first generate a unique system_ID for each patient. This ensures that no requests include the patient’s original identifiers, which may contain or be linkable to personally identifiable information (PII). Instead, we store an encrypted representation of the original identifier along with the associated System ID. This is used exclusively to track the number of unique patient API calls and to support traceability and observability in case providers need to audit their use of the System Clinical Graph APIs.

Developers are responsible for maintaining a crosswalk between their internal patient identifiers and the corresponding System IDs. We do not store the original patient identifiers in any form.