cardiacsense

n8n community nodes for Cardiacsense FHIR API - cardiac and health monitoring data integration

Package Information

Released: 8/6/2025
Downloads: 9 weekly / 33 monthly
Latest Version: 0.1.6
Author: paolo-trivi

Available Nodes

Cardiacsense icon
Cardiacsense
No description available

Documentation

n8n-nodes-cardiacsense

This is an n8n community node. It lets you use Cardiacsense FHIR API in your n8n workflows.

Cardiacsense is a comprehensive cardiac and health monitoring platform that provides real-time access to vital signs, heart rate data, cardiac conditions detection, and advanced cardiovascular metrics through FHIR-compliant APIs.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

The Cardiacsense node supports the following categories of operations:

Vital Signs

  • Get Blood Glucose - Retrieve glucose concentration measurements
  • Get Blood Pressure - Get complete blood pressure readings
  • Get Body Temperature - Retrieve patient body temperature data
  • Get Body Weight - Get patient weight measurements
  • Get Heart Rate (Pulse Oximetry) - Heart rate via pulse oximetry
  • Get Oxygen Saturation - SpO2 measurements from pulse oximetry
  • Get Respiratory Rate - Breathing rate data

Heart Rate Data

  • Get Beat-to-Beat - Real-time heart rate measurements
  • Get 1-Hour Average - Heart rate averaged over 1 hour
  • Get 10-Minute Mean - 10-minute heart rate averages
  • Get 8-Hour Mean - 8-hour heart rate averages
  • Get 10-Hour Mean - 10-hour heart rate averages
  • Get 12-Hour Average - 12-hour heart rate averages
  • Get 24-Hour Mean - Daily heart rate averages

Cardiac Conditions

  • Get Atrial Fibrillation - Atrial fibrillation detection data
  • Get Tachycardia - Fast heart rate detection
  • Get Bradycardia - Slow heart rate detection

Activity Data

  • Get Sleep Data - Sleep quality and duration metrics
  • Get Steps Data - Physical activity step counts
  • Get Calories Data - Energy expenditure measurements

Advanced Metrics

  • Get Real-Time Data - Live monitoring data streams
  • Get Pulse Wave Velocity - Arterial stiffness measurements
  • Get Night RRV Data - Nocturnal respiratory rate variability
  • Get Perfusion Index - Blood perfusion measurements

Patient Management

  • List Patients - Retrieve detailed patient list
  • Get Patient Physicians - Patient-doctor relationship data

Credentials

To use the Cardiacsense node, you need to configure the following credentials:

Prerequisites

  • An active Cardiacsense integrator account
  • API access token from Cardiacsense

Authentication Setup

  1. Obtain your API token from your Cardiacsense integrator dashboard
  2. In n8n, create new Cardiacsense API credentials
  3. Enter your API token in the "API Token" field
  4. Configure the base URL:
    • Base URL: Your Cardiacsense FHIR API endpoint (default: https://fhir.cardiacsense-cloud.com)

The node uses Bearer token authentication for all API requests.

Compatibility

  • Minimum n8n version: 0.198.0
  • Tested with: n8n v1.0.0+
  • Node API version: 1

This node follows FHIR standards and uses LOINC/SNOMED-CT medical coding systems for data type identification.

Usage

Basic Workflow Example

  1. Add the Cardiacsense node to your workflow
  2. Select a resource (e.g., "Vital Signs")
  3. Choose an operation (e.g., "Get Heart Rate")
  4. Configure parameters:
    • Patient Email: patient@example.com
    • Start Time: 2024-01-01
    • End Time: 2024-01-02
  5. Optional settings:
    • Averaging Interval: Set time averaging in minutes
    • Ignore Metadata: Toggle for simplified response format

Data Format

The node returns data in two formats:

FHIR-compliant format (default):

[
	{
		"valueQuantity": {
			"value": "72.0"
		}
		// ... additional FHIR metadata
	}
]

Simplified format (when "Ignore Metadata" is enabled):

{
	"data": [
		{
			"value": "72.0"
		}
	]
}

Time Range Specifications

  • Dates can be in YYYY-MM-DD format
  • Date-time can be in YYYY-MM-DD HH:MM:SS format
  • All times are processed according to the patient's configured timezone

Resources

Discussion