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 advanced cardiovascular and health monitoring metrics for patients. Specifically, the "Get Pulse Wave Velocity" operation fetches pulse wave velocity data—a key indicator of arterial stiffness and cardiovascular health—over a specified time range for a given patient.
Use cases include:
- Monitoring cardiovascular health trends in patients over time.
- Analyzing arterial stiffness changes in response to treatments or lifestyle changes.
- Integrating pulse wave velocity data into broader health analytics workflows.
For example, a healthcare provider could use this node to automatically pull pulse wave velocity measurements from a patient's wearable device data within a defined date range to assess cardiovascular risk.
Properties
| Name | Meaning |
|---|---|
| Patient Email | Email address of the patient whose 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: |
| - Averaging Interval (Minutes) | Time averaging interval in minutes (0-60) to smooth the data. |
| - Ignore Metadata | Boolean flag to return simplified response without FHIR metadata. |
| - Device | Device type where measurement originated: CardiacSense Watch, External Device, or Manual by User. |
| - AF Source | Source for atrial fibrillation detection (only relevant for other operations, not this one). |
Output
The node outputs an array of JSON objects representing the pulse wave velocity data points retrieved from the Cardiacsense API. Each object corresponds to a measurement or aggregated data point within the specified time range.
If the "Ignore Metadata" option is set to true, the output excludes FHIR metadata fields, providing a simplified dataset focused on the core measurement values.
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 network access to the Cardiacsense API endpoints.
- No additional environment variables are required beyond the API authentication token.
Troubleshooting
Common Issues:
- Invalid or missing patient email will cause the API request to fail.
- Incorrect date/time formats for start or end times may result in errors or empty responses.
- Using an unsupported device type or invalid averaging interval can lead to unexpected results.
Error Messages:
"Unknown operation: getPulseWaveVelocity": Indicates the operation name is incorrect or not supported; verify spelling and case."Unknown patient management operation": Occurs if the resource-operation combination is mismatched.- HTTP errors related to authorization usually mean the API token is invalid or expired; reauthenticate the API credentials.
- Network errors suggest connectivity issues to the Cardiacsense API endpoint.
To resolve these, ensure all required properties are correctly filled, validate date/time formats, and confirm that the API credentials are current and have proper permissions.