/ prevent

Prevent 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.

Create a new patient

post
/v1/patient

Create a new patient.

Authorizations
x-api-keystringRequired
Body

Patient Input Model.

unique_patient_identifierstringRequired

Unique Patient Identifier

Responses
post
/v1/patient
POST /v1/patient HTTP/1.1
Host: cg-api-prod.system.com
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 36

{
  "unique_patient_identifier": "text"
}
{
  "system_id": "text"
}

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.

Get recommendations for a patient

post
/v1/patient/{system_id}

Get recommendations for a patient.

Authorizations
x-api-keystringRequired
Path parameters
system_idstringRequired
Body

Schema for Assemble input.

patient_system_idany ofRequired
stringOptional
or
nullOptional
patient_biomarkersany ofOptional
objectOptional
or
nullOptional
patient_historyany ofOptional
objectOptional
or
nullOptional
patient_demographicsany ofOptional
or
nullOptional
Responses
post
/v1/patient/{system_id}
POST /v1/patient/{system_id} HTTP/1.1
Host: cg-api-prod.system.com
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 114

{
  "patient_system_id": "text",
  "patient_biomarkers": {},
  "patient_history": {},
  "patient_demographics": {
    "sex": 1,
    "age": 1
  }
}
[
  {
    "system_id": "text",
    "modifiable_factor": "text",
    "ranking_score": 1,
    "relationships": [
      {
        "relationship_id": "text",
        "notable_target": "text",
        "relationship_metadata": {
          "sign": "text",
          "num_findings": 1,
          "num_significant_findings": 1,
          "num_studies": 1,
          "highest_cited": 1,
          "highest_sample_size": 1,
          "num_experimental_trials": 1,
          "median_effect_size": 1
        },
        "relationship_summary": "text",
        "dois": [
          "text"
        ]
      }
    ]
  }
]

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.

PreviousClinical Graph

Last updated

Was this helpful?