@rahul1 I shared this query earlier in DM, but sharing it here as well for quick response. We are trying to create a Client in Medplum for wearable devices such as Fitbit, Google Fit, etc. The patients can connect and authenticate wearable devices like Google Fit and retrieve their vitals & store data from these devices in medium observation resources. So my query is where we can store the wearable devices access token for the patients. We were thinking of using the link [extension] parameter in the patient resource https://www.medplum.com/docs/api/fhir/datatypes/extension for storing the Fitbit access token of the patient user. So I wanted to confirm if this is the right approach.

@Ankit Yadav checkout the FHIR

Device

resource as it might be a more idiomatic/FHIR-compliant resource. https://hl7.org/fhir/device.html https://www.medplum.com/docs/api/fhir/resources/device The access token could be stored as an extension on the

Device

resource directly.

We have a slightly different use case for our users and implementation but we utilized the

Device

resource and then stored push token and biometric public key as extensions on the resource. It's been working well for us.