Actions26
- Activity Data Actions
- Advanced Metrics Actions
- Cardiac Conditions Actions
- Heart Rate Data Actions
- Patient Management Actions
- Vital Signs Actions
Overview
This node integrates with the Cardiacsense FHIR API to retrieve cardiac and health monitoring data, specifically focusing on activity-related metrics such as sleep, physical activity, and lifestyle measurements. The "Get Steps Data" operation under the "Activity Data" resource fetches step count data for a specified patient within a given time range.
Common scenarios where this node is beneficial include:
- Monitoring patient physical activity remotely by healthcare providers.
- Integrating step count data into broader health analytics workflows.
- Tracking rehabilitation progress or daily activity levels in clinical studies.
For example, a healthcare provider can use this node to automatically pull step data for a patient over the past week to assess their mobility and recovery status.
Properties
| Name | Meaning |
|---|---|
| Patient Email | Email address of the patient whose steps data is being requested. |
| Start Time | Start date/time for the data query in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format. |
| End Time | End date/time for the data query in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format. |
| Additional Options | Collection of optional parameters to customize the request: |
| - Averaging Interval (Minutes) | Time averaging interval in minutes (0-60) to aggregate step data. |
| - Ignore Metadata | Boolean flag to return simplified response without FHIR metadata. |
| - Device | Device type from which the measurement originated. Options: CardiacSense Watch, External Device, Manual by User. |
| - AF Source | (Not applicable for Get Steps Data; relevant only for atrial fibrillation detection operations.) |
Output
The node outputs an array of JSON objects representing the steps data retrieved from the Cardiacsense API. Each object corresponds to a data point within the specified time range and includes fields such as step counts and timestamps.
If the "Ignore Metadata" option is set to true, the output excludes detailed FHIR metadata, providing a simplified dataset focused on core step information.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Cardiacsense FHIR API.
- The node expects valid credentials configured in n8n with access tokens and base URLs for the Cardiacsense service.
- Network connectivity to the Cardiacsense API endpoints is necessary.
Troubleshooting
Common Issues:
- Invalid or expired API token leading to authentication errors.
- Incorrect date/time formats causing request failures.
- Missing required parameters like patient email or time range.
- Unsupported device types or invalid averaging intervals.
Error Messages:
"Unknown operation: getStepsData": Indicates the operation name might be misspelled or not supported."Unknown patient management operation": Occurs if the resource-operation combination is incorrect.- HTTP errors from the API (e.g., 401 Unauthorized, 400 Bad Request) usually relate to credential issues or malformed requests.
Resolutions:
- Verify and refresh API credentials.
- Ensure date/time inputs follow the specified format.
- Confirm all required properties are provided.
- Use supported device options and valid numeric values for intervals.
Links and References
- Cardiacsense Developer Documentation (hypothetical link for reference)
- FHIR Standard Overview
- n8n Documentation on Creating Custom Nodes