Add a credential to login the FHIR REST interface - in this case only consider a basic authentication
.png)
.png)
Add Service Registry - in this case only consider a basic authentication
- setup a HTTP service
- input the Path to the FHIR Server
- input the URL to the FHIR service
- use the credential profiled
.png)
Add a "HS.FHIRServer.Interop.HTTPOperation"
.png)
Choose the Service Name
.png)
Test the FHIR Client
.png)
.png)
Trace the test result
.png)
.png)
.png)
Great Article， Kate！ Could you pls translate and also post on CN DC？ Thx！
Sure, let me do it on Friday
@Kate Lau
This is wonderful! Thanks alot!
I have not looked at the class reference so please pardon me if my questions are basic! But how would you modify the request to add things like modifiers and parameters? Would they be placed in the Request Path String? Also, if this client authenticates with the FHIR Repository through certificates, how is that handled?
Thank you
I know this is not using OAuth, but OAuth is just the Authentication method.
When I attempt to do something similar to search Patient for identifier=OSUMRN|xxxxx I keep getting a 404 not found error. Nothing is showing up within the ISCLOG under %SYS globals. Is there anyway I can see the trace of making the calls to verify that the correct API's are being called in the correct format? What is the magic chant to get the ISCLOG to capture the information?
I use these globals to take a peak at the calls:
zn "YOURFHIRNAMESPACE" Set ^FSLogChannel("all")=1 zn "%SYS" Kill ^%ISCLOG Kill ^ISCLOG Set ^%ISCLOG=5 Set ^%ISCLOG("Category","HSFHIR")=5 Set ^%ISCLOG("Category","HSFHIRServer")=5 Set ^%ISCLOG("Category","OAuth2")=5 Set ^%ISCLOG("Category","OAuth2Server")=5then
zw ^FSLOGin the fhir namespace.
Shows the route, params and helpful with oauth2/SMART where the route has to match the patientid in the token.
when I tried a
zw ^FSLOGnothing is written out...