Elation Health · Schema

PatchedPatientProviderTeamMemberUpdate

HealthcareUnited StatesElectronic Health RecordsFHIRHL7InteroperabilitySMART on FHIRPrimary CareValue-Based CareEligibilityClinical DataSchedulinge-PrescribingDigital HealthA2A

Properties

Name Type Description
activity_summary_last_refreshed string The last known time when this team member's activity was synced.
earliest_activity string Displays the earliest known interaction between the team member and the patient.
group object Can either be `main` or `other`. By default members are placed in the `main` group. Only members in the `main` group will be displayed on the Patient chart in the web application. * `main` - main * `o
latest_activity string Displays the latest known interaction between the team member and the patient.
patient_id integer The id of the Patient that this team is associated with.
patient_provider_team_id integer Patient Provider team ID
patient_provider_team_member_id integer
physician_id integer The Physician that this team member represents.
rank integer Used for displaying a sorted patient provider team in the patient chart. Rank is sequential and begins at 1.
treatment_reason stringnull The reason why this physician is in this team
View JSON Schema on GitHub

JSON Schema

elation-health-patched-patient-provider-team-member-update-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/elation-health/main/json-schema/elation-health-patched-patient-provider-team-member-update-schema.json",
  "title": "PatchedPatientProviderTeamMemberUpdate",
  "x-generated": "2026-10-12",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/elation-health-provider-team-api-openapi.yml#/components/schemas/PatchedPatientProviderTeamMemberUpdate",
  "properties": {
    "activity_summary_last_refreshed": {
      "description": "The last known time when this team member's activity was synced.",
      "format": "date-time",
      "readOnly": true,
      "type": "string"
    },
    "earliest_activity": {
      "description": "Displays the earliest known interaction between the team member and the patient.",
      "format": "date-time",
      "readOnly": true,
      "type": "string"
    },
    "group": {
      "allOf": [
        {
          "$ref": "#/$defs/GroupEnum"
        }
      ],
      "default": "main",
      "description": "Can either be `main` or `other`. By default members are placed in the `main` group. Only members in the `main` group will be displayed on the Patient chart in the web application.\n\n* `main` - main\n* `other` - other"
    },
    "latest_activity": {
      "description": "Displays the latest known interaction between the team member and the patient.",
      "format": "date-time",
      "readOnly": true,
      "type": "string"
    },
    "patient_id": {
      "description": "The id of the Patient that this team is associated with.",
      "readOnly": true,
      "type": "integer"
    },
    "patient_provider_team_id": {
      "description": "Patient Provider team ID",
      "readOnly": true,
      "type": "integer"
    },
    "patient_provider_team_member_id": {
      "readOnly": true,
      "type": "integer"
    },
    "physician_id": {
      "description": "The Physician that this team member represents.",
      "readOnly": true,
      "type": "integer"
    },
    "rank": {
      "description": "Used for displaying a sorted patient provider team in the patient chart. Rank is sequential and begins at 1.",
      "minimum": 1,
      "readOnly": true,
      "type": "integer"
    },
    "treatment_reason": {
      "description": "The reason why this physician is in this team",
      "type": [
        "string",
        "null"
      ]
    }
  },
  "type": "object",
  "$defs": {
    "GroupEnum": {
      "description": "* `main` - main\n* `other` - other",
      "enum": [
        "main",
        "other"
      ],
      "type": "string"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/elation-health-patched-patient-provider-team-member-update"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.