I am trying to form a request like :
http://host/api/FHIR/DSTU2/Schedule?Schedule.actor:Practitioner=1234&Schedule.actor:Practitioner.location=5678&slottype=urn:oid:1.2.3|PrimaryCare&start=2016-08-08
Using HAPI FHIR Java API, how can I parse following params :
Schedule.actor:Practitioner=1234
Schedule.actor:Practitioner.location=5678
This is definitely supported.
Assuming you're creating a server, you would want a parameter on your resource provider method like:
#IncludeParam(allow={"Schedule:actor","Schedule:practitioner"})
Set<Include> theIncludes
Add "*" to the list of strings to just whitelist anything
Related
Is there a suitable package to be able to use the FHIR standard in Golang? There should be a small dependency on the Google Cloud.
One way of using FHIR in Golang is the FHIR Protocol Buffers implementation: https://github.com/google/fhir
This includes a Golang parser/serializer for JSON to protobuf, which will get you language-specific data structures. It doesn't include a library for the FHIR REST API but you can use standard http libraries for that.
I know I can add a /v3/api-docs/ to the end of my APIs endpoint to get a JSON representation of my APIs schema.
Is there a way to get the schema for a specific version of the API?
In our case, we have a versioned API.
The below URI was our entire JSON schema including all API versions.
.../v3/api-docs
But, the below URI was scoped only to a specific API version.
.../v3/api-docs/v2-tool
The v2-tool corresponds to a namespace specific to our code.
I am trying to define a contract using spring-cloud-contract framework that for a specific request returns a response with big body. This body is always the same. So I would prefer to store this body in some static file. And generated Wiremock mapping would use bodyFileName to refer to that static file with response body content.
No it doesn't. But the DSL uses Groovy so you could theoretically download the body from somewhere. From the jar with stubs for example
I am creating OData endpoints using ASP.NET Web API using v5.8.0 of this NuGet package. I have everything working and I can retrieve simple data such as strings and ints without an issue. However I would now like to extend one of the endpoints so that one of the items that can be retrieved is a binary image file. Having read up on OData I have decided to use named resource streams to achieve this.
The problem I have is that I can find very little information on how to implement this using the ODataController. The closest I can find is this blog post but it is using an older version of Web API and the code does not compile when I use it in my project.
So can somebody please supply a working example of how this should be implemented please.
Named streams (aka stream properties) are not currently supported in Web API OData (for OData v4). See the following issues:
Clarify the situation for streams
Document for Stream Support in OData V4
I want to use OData in Web Api for few Action methods in a Controller. What is happening is that once i enable OData in Web Api, the error message format is getting changes for all error .
Is there any way to configure Odata only for specific controller/action routes.
Error Message before Enabling OData looks like:
{"Message":"User Name/Password are invalid ."}
Error Message after Enabling OData looks like:
{
"odata.error":{
"message":{
"lang":"en-US","value":"User Name/Password are invalid ."
}
}
}
I would like to configure OData to handle only specific controllers so that rest of the APIs have no impact of OData setting. Your help is appreciated.
One of the big changes we made between RC and RTM is that we've completely removed the EnableOData extension method. We realized that registering OData formatters globally was a bad idea because it impacts controllers regardless of whether they're meant to be OData controllers.
So, in our v1 release for OData and in our current nightly builds, we've added a new base class called ODataController. If you derive from ODataController (or EntitySetController), you will automatically get support for OData just for that controller. It shouldn't affect the rest of your controllers the way it does now. You should also use config.Routes.MapODataRoute instead of EnableOData.
You can install our latest nightly build using these instructions:
http://blogs.msdn.com/b/henrikn/archive/2012/06/01/using-nightly-asp-net-web-stack-nuget-packages-with-vs-2012-rc.aspx
It should be pretty stable at this point.