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 vital signs data, specifically focusing on cardiac and health monitoring metrics. The "Get Respiratory Rate" operation under the "Vital Signs" resource allows users to fetch respiratory rate measurements for a specified patient within a defined time range.
Common scenarios where this node is beneficial include:
- Remote patient monitoring where healthcare providers need to track respiratory rates over time.
- Clinical research requiring aggregated respiratory data from wearable or external devices.
- Health applications that integrate patient vital signs into dashboards or alerting systems.
For example, a healthcare provider can use this node to pull respiratory rate data recorded by a CardiacSense Watch for a patient between January 1st and January 2nd, 2024, to analyze trends or detect anomalies.
Properties
| Name | Meaning |
|---|---|
| Patient Email | Email address of the patient whose respiratory rate 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 respiratory rate data. |
| - Ignore Metadata | Boolean flag to return a simplified response without FHIR metadata. |
| - Device | Device type for measurement origin; options are: |
| • CardiacSense Watch | |
| • External Device | |
| • Manual by User |
Output
The node outputs an array of JSON objects representing respiratory rate measurements retrieved from the Cardiacsense API. Each object contains the respiratory rate data points along with associated metadata unless the "Ignore Metadata" option is enabled, which simplifies the output by removing FHIR-specific metadata.
If binary data were involved (e.g., waveform files), it would be included as binary attachments, but this operation focuses on JSON-formatted vital sign data only.
Dependencies
- Requires an API key credential for authenticating with the Cardiacsense FHIR API.
- The node expects proper configuration of the API base URL and authorization token via credentials.
- Network access to the Cardiacsense API endpoints is necessary.
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 unsupported device types or invalid averaging intervals could lead to unexpected results.
Error Messages:
"Unknown operation: getRespiratoryRate": Indicates the operation name is not recognized; verify spelling and case."Unknown patient management operation": Occurs if the resource or operation combination is incorrect.- HTTP errors such as 401 Unauthorized suggest issues with API credentials.
Resolutions:
- Ensure all required properties are correctly filled.
- Validate date/time inputs conform to expected formats.
- Confirm API credentials are valid and have necessary permissions.
- Use the "Ignore Metadata" option if FHIR metadata complicates downstream processing.