Welcome to fhir-server Discussions!

[CaitlinV39]

👋 Welcome to the Microsoft FHIR Server discussion page

We’re using Discussions as a place to connect with other members of our community. We're hoping that this will be a good place for discussions around the use of our specific implementation of the FHIR service. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community. We hope this will supplement the http://chat.fhir.org which is the official community space for FHIR questions.

We have documentation on the open-source site and additional documentation on our managed service here: https://docs.microsoft.com/azure/healthcare-apis/fhir/

[WiktorNowikow]

Hii, dear @CaitlinV39 !
If I understood right, that controller: https://github.com/microsoft/fhir-server/blob/main/src/Microsoft.Health.Fhir.Shared.Api/Controllers/FhirController.cs is the example? Or only this one controller will work with all resources and API is complete to use? Or I must realize my endpoints for my resources by myself?
Kind Regards
Victor

[Ivanidzo4ka]

only this one controller will work with all resources and API is complete to use

It depends what do you mean by this. Would it be only place which we add API calls to a system? No, we have for example ValidateController. But probably 99% of the calls you gonna make will go through that controller.

Also we use quite thin controllers, main goal of them to take incoming request and parse data, rest of the logic implemented via mediator library and work with resources happens in respectful handler.

[WiktorNowikow]

Thank you for your answer. Yes, I found, why only one controller for resources there - because all of them keeps in one table.
Is it possible for me to create different endpoints for different resources or that project is not so flexible for such changes?

[Ivanidzo4ka]

Everything is possible, question is it right way to achieve your goal?

There is ~150 different resources in FHIR spec, to have one endpoint for each of them is quite burdensome task.

As I say, we treat controller as a thin entity which does only parsing of data and just pass that data to mediator, and mediator library allow you to define pipeline behavior which can look on resource type and do some extra work required, or just override behavior.

For example this one creates additional Providence resource for any incoming resource: https://github.com/microsoft/fhir-server/blob/main/src/Microsoft.Health.Fhir.Shared.Api/Features/Resources/ProvenanceHeaderBehavior.cs

Or this one which does extra logic for SearchParameter resource: CreateOrUpdateSearchParameterBehavior

[WiktorNowikow]

Thank you for your response!
Yes, your architecture of the application is very interesting, and a lot of things are not clear for me, I use the MediatR library for my CQRS architecture, but it works pretty simply in my case. And yes, you are right, it is very simple but I write a lot of similar code for different endpoints. Where are can read more about that kind of architecture?
Maybe I will find some answers about how I can use common handlers for CRUD.
By the way, I am trying to run your fhir-server with SqlStore option in Visual Studio, on the last step I had generated DB with sqlcmd from SQL scripts include that script: https://github.com/microsoft/healthcare-shared-components/blob/master/src/Microsoft.Health.SqlServer/Features/Schema/Migrations/BaseSchema.sql , because the application didn't generate DB automatically.
But I still have errors, when I am trying to request metadata.
https://gist.github.com/WiktorNowikow/e90892db8df4dbceb7ac94ac2bb2096c

Do you have any advice on how I can set up that option?

Best Regards