Clinical Document Exchange
A 4-step recipe with Particle Health. We can help you get access.
Recipe · 4 steps
Clinical Document Exchange
with Particle Health · Health Information Management
Push a clinical document and confirm it by reading it back and listing the patient's documents.
- Exchange the client credentials for a bearer token used by every subsequent call.
- Push the clinical document into the network for the patient.
- Read the stored document back by id to confirm it was received and indexed.
- List every document currently on file for the patient.
What you'll need to have ready
- clientId: Particle client id used to obtain a bearer token.
- clientSecret: Particle client secret used to obtain a bearer token.
- particlePatientId: The Particle patient id the document belongs to.
- document: The clinical document payload (content, type, and metadata) to submit.
For your developer
Arazzo workflow particle-health:clinical-document-exchange, 4 operations: getAuthToken → submitDocument → getDocument → getPatientDocuments. Specs on APIs.io.