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 information related to patient management, specifically focusing on obtaining the list of physicians associated with a given patient. It is useful in healthcare workflows where you need to programmatically access or verify which physicians are linked to a particular patient based on their email address.
A practical example would be a hospital automation system that, upon receiving a patient's email, fetches all their attending physicians to coordinate care or send notifications.
Properties
| Name | Meaning |
|---|---|
| Patient Email | The email address of the patient whose associated physicians you want to retrieve. |
Output
The output is a JSON array containing the data returned by the Cardiacsense API endpoint for patient physicians. Each item in the array represents a physician associated with the specified patient. The exact structure depends on the API response but typically includes physician details such as name, contact information, and role.
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 the API token and base URLs to be configured in the 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 or expired API authentication token will result in authorization errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
Unknown patient management operation: This indicates the operation parameter is not recognized; ensure "Get Patient Physicians" is selected.- HTTP errors from the API (e.g., 401 Unauthorized) suggest problems with credentials.
- If the node throws an error about missing parameters, verify that the "Patient Email" field is correctly filled.
Resolutions:
- Double-check the patient email format and presence.
- Verify and update the API key credential if needed.
- Ensure the node has internet access and the Cardiacsense API is reachable.
Links and References
- Cardiacsense API Documentation (hypothetical link, replace with actual if available)
- FHIR Standard Overview