FHIR Facade Integration?
# support
l
Hello! Is there a way to use Medplum with a FHIR facade? For context, I'm using the FHIR R4 format and self-hosting my Medplum server through AWS (https://www.medplum.com/docs/self-hosting/install-on-aws). Since it's hosted through AWS using the CDK, I'm not aware of any direct code that I can access for the UI or backend for my Medplum server, but I would like to start off by overriding a simple Patient GET request. If there's any more details I should provide, please let me know, thanks!
@rahul1 would you happen to have any insight on this matter? Essentially, our team simply needs to be able to override the API routes programmatically, but we're not sure where the code is located after self-hosting it on AWS, or how to edit it for our own use. Any help on this matter would be greatly appreciated!
r
Bots might be reasonable for this?
r
HI @lookatericman , sorry for the delay. I think I might need a bit more context to answer this correctly
What kind of override would you like to make on Patient GET
in general, FHIR spec standardizes the data schema AND the endpoint urls/parameters.
Those users who would like to add custom urls in front of the Medplum server tend to either: 1. Run their own HTTP proxy that reshapes and forwards HTTP requests 2. Use Bots as custom endpoints, having clients use the
$execute
endpoint
l
Hi @rahul1 thanks a lot for getting back to me. So we’re trying to build a FHIR facade that will act as a translation layer to go against a proprietary database. Since the self-hosted AWS CDK (https://www.medplum.com/docs/self-hosting/install-on-aws#cdk-deploy) deploys everything in AWS automatically, it essentially leaves the questions of: where exactly do we go to augment the code or reroute it to implement our own logic? Furthermore, is it something we can write in, say, Express.js? After some discussion with my team, my use of the word “override” may have been excessive, but is accurate to the sense that rather than implementing from an internal Medplum data structure, we want to reroute it for our own translation, all while still maintaining FHIR semantics. Additionally, I only brought up the Patient GET route as a very simple example where we could first test it working at all, where we will then look into expanding our translation layer to the rest of the API. If what I described is not possible, that is fine, but it would be great to know. And if you would like some more details or context, please let me know. Thanks again!
r
Ah I see now. If I understand correctly, the goal is for: Client --> Medplum API --> Proprietary, non-FHIR data setore Is that right?
If so, Medplum would not be the best tool for this job. Our API service is tightly coupled to our DB schema, which allows us to maintain performance and scalability
181 Views