Kate Lau · Jan 18 go to post

I encountered 401 before and I go to 

System > Security Management > View Audit Database

and check that the token passed the authentication server, so at that moment I suspect it doesn't pass the fhir server. After asking the support, we found out that, when checking out the token, we need to add the correct audience and scope (user/*.read user/*.write) to make it work.

**example**
Access Token URL  :  https://www.somewhere.com/oauth2/token?aud=https://www.somewhere.com/cs…

Scope : user/*.read user/*.write

with corresponding client_id and client_secret

and check out the token. after that, it can pass the fhir server authentication

Kate Lau · Oct 28, 2025 go to post

Oooo, this is a good suggestion!!😮 I have never think about this direction before.

Because at the beginning, I only want to write some stuff for facilitating my testing process on the FHIR repository. So I use the python library for generating some fake data and put it on a REST service...
For using it as a facade... maybe a possible way as well, maybe can replace the generated data by loading the "REAL" data from the IRIS db, right?

Kate Lau · Oct 28, 2025 go to post

It is just an example for generating FHIR bundle for testing purpose, we still need a FHIR server for storing the data

Kate Lau · Dec 31, 2024 go to post

I just wondering if there is any easy way to add the header in our build in BO..... because what I found that different REST API do have slightly different in the header requirement... which means that our users do need this kinds of flexibility  when they would like to be a REST client.....

Kate Lau · Mar 15, 2023 go to post

In fact I encountered the error of unable to pass the variable to

"ISC_IRIS_URL", "ISC_IAM_IAMGE","ISC_CA_CERT"

I suspect that the iam-setup.sh now working very well

As a work around, I hard code the variables in the docker-compose.yml

and run the 

sudo docker compose up -d 

again