Stream: implementers
Topic: FHIR Server URL paths for owned resources
John Josef (May 08 2019 at 13:57):
I'd like to implement my FHIR server with a structure like this, so that Patients have their own scope and logically this makes more sense to me.
/Patient/{patientId}/{Resource}
eg: /Patient/1234/Medication instead of /Medication?subject=Patient/1234
Basically, wondering if something like this is acceptable or not. Didn't see anything in the docs about chaining resources like this
Michele Mottini (May 08 2019 at 14:02):
Yes, it is acceptable and already exists: http://hl7.org/fhir/compartmentdefinition.html
John Josef (May 08 2019 at 14:03):
Thank you!
Lloyd McKenzie (May 08 2019 at 14:14):
Be aware that it's not necessarily widely supported.
Grahame Grieve (May 08 2019 at 14:22):
the vast majority of health record systems deal seamlessly with resources across different patients. In these systems, compartmenting records by patient doesn't happen and URL patterns like that are problematic. The question you are asking is typical or personal health records. You can do it on a microservice basis, where all the records for a single patient are one FHIR end-point
Grahame Grieve (May 08 2019 at 14:29):
the compartment definition reference is actually not the same thing
Last updated: Apr 12 2022 at 19:14 UTC
