Elation Health Family Histories API

The Family Histories API from Elation Health — 4 operation(s) for family histories.

Documentation GitHub OpenAPI

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /family_histories/{id}/ Get a family history entry (Get) · Get Family History #

Ask an LLM

“How do I get one family history entry for a patient?”

“Can I get the relationship on a family history record?”

Tell an agent

Get family history {id}.

Get the relative and condition on family history {id}.

DELETE /family_histories/{id}/ Delete a family history entry (legacy) · Delete Family History #

Ask an LLM

“How do I delete a family history entry with the older call?”

“Can I remove a wrong family history item?”

Tell an agent destructive · confirm first

Delete family history {id} with the legacy call.

Remove incorrect family history item {id}.

GET /family_histories/ Find a patient's family history · Find Family Histories #

Ask an LLM

“What conditions run in a patient's family?”

“Can I find all family history entries for one patient on the legacy endpoint?”

Tell an agent

Find family history for patient {patient}.

Find what conditions relatives of {patient} had.

POST /family_histories/ Add a family history entry (legacy) · Create Family History #

Ask an LLM

“How do I add a relative's condition with a SNOMED code using the older create?”

“Can I rank family history entries when adding them?”

Tell an agent

Add family history for {patient} via the legacy endpoint: {relationship} had {text}.

Legacy-add family history for {patient}, relative {relationship}, SNOMED {snomed_code}, rank {rank}.

GET /api/2.0/family_histories/ List family histories with paging · List Family Histories #

Ask an LLM

“Can I page through family histories across a practice?”

“How do I list family history entries sorted by rank in the v2.0 API?”

Tell an agent

List family histories for practice {practice}, {limit} per page.

List family histories of {patient} ordered by {order_by}.

POST /api/2.0/family_histories/ Create a family history entry · Create Family History #

Ask an LLM

“Do I send text or an ICD-9 code when creating a family history in the v2.0 API?”

“What happens if I send both text and a code for a family history entry?”

Tell an agent

Create family history for {patient}: {relationship}, ICD-9 {icd9_code}.

Create a free-text family history for {patient}, {relationship}: {text}.

DELETE /api/2.0/family_histories/{id}/ Delete a family history entry · Delete Family History #

Ask an LLM

“How do I delete an existing family history by id?”

“Can a family history record be destroyed?”

Tell an agent destructive · confirm first

Delete existing family history {id}.

Destroy family history record {id}.

GET /api/2.0/family_histories/{id}/ Retrieve a family history entry · Retrieve Family History #

Ask an LLM

“Can I retrieve one family history entry with its codes?”

“Where do I retrieve a family history's ICD-9 or SNOMED code?”

Tell an agent

Retrieve family history {id}.

Retrieve the codes on family history {id}.

Work with this as data

Every API 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 apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
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 API

curl "https://apis.io/api/v1/apis/elation-health:elation-health-family-histories-api"

All apis

curl "https://apis.io/api/v1/apis?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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Elation Health Family Histories API
  version: '1.0'
  description: 'Operations tagged Family Histories across 2 of this provider''s published API definitions: elation-api-settings.json, elation-health-api-full-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://sandbox.elationemr.com/api/2.0
- description: Sandbox Server
  url: https://sandbox.elationemr.com
- description: Production Server
  url: https://api.app.elationemr.com
tags:
- name: Family Histories
paths:
  /family_histories/{id}/:
    get:
      summary: Get Family History
      description: ''
      operationId: get-family-history
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: integer
          format: int64
      - name: Authorization
        in: header
        required: true
        schema:
          type: string
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                Result:
                  value: "{\n  \"id\": 83792571234,\n  // See Object Definition\n}"
        '400':
          description: '400'
          content:
            application/json:
              examples:
                Result:
                  value: '{}'
              schema:
                type: object
                properties: {}
      deprecated: false
      x-readme:
        code-samples:
        - language: python
          code: "import requests\nimport json\n\naccess_token = \"TyEPKw8fVGRKpCBa81ygwjCLXDNIAm\"\nauth_header = \"Bearer %s\" % (access_token)\n\nresp = requests.get(\"https://sandbox.elationemr.com/api/2.0/family_histories/64184451073/\",\n                    headers={'Authorization': auth_header})\n\nprint resp.status_code\nprint json.dumps(json.loads(resp.content), indent=2)"
        samples-languages:
        - python
      tags:
      - Family Histories
      security:
      - sec0: []
    delete:
      summary: Delete Family History
      description: ''
      operationId: delete-family-history
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: integer
          format: int64
      - name: Authorization
        in: header
        required: true
        schema:
          type: string
      responses:
        '204':
          description: '204'
          content:
            application/json:
              examples:
                Result:
                  value: ''
      deprecated: false
      x-readme:
        code-samples:
        - language: python
          code: "import requests\nimport json\n\naccess_token = \"TyEPKw8fVGRKpCBa81ygwjCLXDNIAm\"\nauth_header = \"Bearer %s\" % (access_token)\n\nresp = requests.delete(\"https://sandbox.elationemr.com/api/2.0/family_histories/54233202689/\",\n                       headers={'Authorization': auth_header})\n\nprint resp.status_code"
        samples-languages:
        - python
      tags:
      - Family Histories
      security:
      - sec0: []
    servers:
    - url: https://sandbox.elationemr.com/api/2.0
  /family_histories/:
    get:
      summary: Find Family Histories
      description: ''
      operationId: find-family-histories
      parameters:
      - name: Authorization
        in: header
        required: true
        schema:
          type: string
      - name: patient
        in: query
        schema:
          type: array
          items:
            type: integer
            format: int64
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                Result:
                  value: "{\n  \"count\": 123,\n  \"next\": \"https://sandbox.elationemr.com/api/2.0/family_histories/?limit=10&offset=10\",\n  \"previous\": \"https://sandbox.elationemr.com/api/2.0/family_histories/?limit=10\",\n  \"results\": [  // list of objects\n    { // See Object Definition },\n    // ...\n    { // See Object Definition },\n  ]\n}"
        '400':
          description: '400'
          content:
            application/json:
              examples:
                Result:
                  value: '{}'
              schema:
                type: object
                properties: {}
      deprecated: false
      x-readme:
        code-samples:
        - language: python
          code: "import requests\nimport json\n\naccess_token = \"VFroUHsmrErlVI6nJ08Alwhri5RGCW\"\nauth_header = \"Bearer %s\" % (access_token)\n\nresp = requests.get(\"https://sandbox.elationemr.com/api/2.0/family_histories/\",\n                    headers={'Authorization': auth_header})\n\nprint resp.status_code\nprint json.dumps(json.loads(resp.content), indent=2)"
        samples-languages:
        - python
      tags:
      - Family Histories
      security:
      - sec0: []
    post:
      summary: Create Family History
      description: ''
      operationId: create-family-history
      parameters:
      - name: Authorization
        in: header
        required: true
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
              - relationship
              - patient
              properties:
                relationship:
                  type: string
                text:
                  type: string
                icd9_code:
                  type: string
                snomed_code:
                  type: string
                patient:
                  type: string
                  description: Patient ID
                rank:
                  type: string
      responses:
        '201':
          description: '201'
          content:
            application/json:
              examples:
                Result:
                  value: "{\n  \"id\": 83792571234,\n  // See Object Definition\n}"
        '400':
          description: '400'
          content:
            application/json:
              examples:
                Result:
                  value: '{}'
              schema:
                type: object
                properties: {}
      deprecated: false
      x-readme:
        code-samples:
        - language: python
          code: "import requests\nimport json\n\naccess_token = \"TyEPKw8fVGRKpCBa81ygwjCLXDNIAm\"\nauth_header = \"Bearer %s\" % (access_token)\n\n# sending only required data\ndata = {\n  \"relationship\": \"Mother\",\n  \"snomed_code\": \"49436004\",\n  \"patient\": 64901939201\n}\n\nresp = requests.post(\"https://sandbox.elationemr.com/api/2.0/family_histories/\",\n                     data=json.dumps(data),\n                     headers={'Authorization': auth_header,\n                              'Content-type': 'application/json'})\n\nprint resp.status_code\nprint json.dumps(json.loads(resp.content), indent=2)\n\n# if you dont have snomed, you can send us free text\n# for example:\ndata = {\n  \"relationship\": \"Mother\",\n  \"text\": \"Cancer\",\n  \"patient\": 64901939201\n}\n"
        samples-languages:
        - python
      tags:
      - Family Histories
      security:
      - sec0: []
    servers:
    - url: https://sandbox.elationemr.com/api/2.0
  /api/2.0/family_histories/:
    get:
      description: Returns a list of patient family histories
      operationId: family_histories_list
      parameters:
      - description: Number of results to return per page.
        in: query
        name: limit
        required: false
        schema:
          type: integer
      - description: The initial index from which to return the results.
        in: query
        name: offset
        required: false
        schema:
          type: integer
      - description: Which field to use when ordering the results.
        in: query
        name: order_by
        required: false
        schema:
          type: string
      - description: Multiple values may be separated by commas.
        explode: false
        in: query
        name: patient
        schema:
          items:
            format: int64
            type: integer
          type: array
        style: form
      - description: Multiple values may be separated by commas.
        explode: false
        in: query
        name: practice
        schema:
          items:
            type: integer
          type: array
        style: form
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PaginatedPatientFamilyHistoryList'
          description: ''
      security:
      - oauth2: []
      summary: List Family Histories
      tags:
      - Family Histories
      x-el8-docs-category: Patient Profile API
      x-el8-docs-versions:
      - '2.1'
      - '2.0'
    post:
      description: You have to specify either `text` or a valid `icd9_code` or a `snomed_code`. If you send `text` along with any of the two codes, the request will be rejected.
      operationId: family_histories_create
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PatientFamilyHistory'
        required: true
      responses:
        '201':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PatientFamilyHistory'
          description: ''
      security:
      - oauth2: []
      summary: Create Family History
      tags:
      - Family Histories
      x-el8-docs-category: Patient Profile API
      x-el8-docs-versions:
      - '2.1'
      - '2.0'
    servers:
    - description: Sandbox Server
      url: https://sandbox.elationemr.com
    - description: Production Server
      url: https://api.app.elationemr.com
  /api/2.0/family_histories/{id}/:
    delete:
      description: Delete an existing family history.
      operationId: family_histories_destroy
      parameters:
      - in: path
        name: id
        required: true
        schema:
          format: int64
          type: integer
      responses:
        '204':
          description: No response body
      security:
      - oauth2: []
      summary: Delete Family History
      tags:
      - Family Histories
      x-el8-docs-category: Patient Profile API
      x-el8-docs-versions:
      - '2.1'
      - '2.0'
    get:
      description: Retrieve a single patient family history
      operationId: family_histories_retrieve
      parameters:
      - in: path
        name: id
        required: true
        schema:
          format: int64
          type: integer
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PatientFamilyHistory'
          description: ''
      security:
      - oauth2: []
      summary: Retrieve Family History
      tags:
      - Family Histories
      x-el8-docs-category: Patient Profile API
      x-el8-docs-versions:
      - '2.1'
      - '2.0'
    servers:
    - description: Sandbox Server
      url: https://sandbox.elationemr.com
    - description: Production Server
      url: https://api.app.elationemr.com
components:
  schemas:
    PatientFamilyHistory:
      properties:
        created_date:
          description: The date the family history was created.
          format: date-time
          readOnly: true
          type:
          - string
          - 'null'
        deleted_date:
          description: The date the family history was deleted.
          format: date-time
          readOnly: true
          type:
          - string
          - 'null'
        icd9_code:
          description: The icd9 code of the family history.
          type:
          - string
          - 'null'
        id:
          readOnly: true
          type: integer
        patient:
          description: The id of the patient.
          format: int64
          type: integer
        rank:
          type: integer
        relationship:
          allOf:
          - $ref: '#/components/schemas/PatientFamilyHistoryRelationshipEnum'
          description: The relationship of the family member of the family history.
        snomed_code:
          description: The SNOMED code for the family history.
          type:
          - string
          - 'null'
        text:
          description: The value (or text) of the family history.
          type: string
      required:
      - patient
      - relationship
      type: object
    PaginatedPatientFamilyHistoryList:
      properties:
        count:
          example: 123
          type: integer
        next:
          example: http://api.example.org/accounts/?offset=400&limit=100
          format: uri
          nullable: true
          type: string
        previous:
          example: http://api.example.org/accounts/?offset=200&limit=100
          format: uri
          nullable: true
          type: string
        results:
          items:
            $ref: '#/components/schemas/PatientFamilyHistory'
          type: array
      required:
      - results
      type: object
    PatientFamilyHistoryRelationshipEnum:
      enum:
      - Aunt
      - Brother
      - Daughter
      - Father
      - Grandfather
      - Grandmother
      - Mother
      - Other
      - Sister
      - Son
      - Uncle
      type: string
  securitySchemes:
    sec0:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://example.com/oauth2/token
          scopes: {}
    oauth2:
      flows:
        clientCredentials:
          scopes:
            act_as_user: Impersonate a provider via X-On-Behalf-Of (combinable with apiv2 or system scopes)
            apiv2: Full access to the API
            system/{resource_name}.read: Read access to a specific resource
            system/{resource_name}.write: Write access to a specific resource
          tokenUrl: /api/2.0/oauth2/token/
      type: oauth2
x-refined-from:
- elation-api-settings.json
- elation-health-api-full-openapi.yaml
x-readme:
  headers: []
x-readme-fauxas: true

Elation Health Family Histories API

Operations 8

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

MCP server

Tools for apis

Call it yourself

Get an API key

OpenAPI Specification