Stream: smart
Topic: User resource?
Yunwei Wang (Apr 04 2018 at 17:07):
We download SMART server from smarthealthit.org. In the metadata, there is a User Resource. But I cannot find any definition in FHIR spec.
Lloyd McKenzie (Apr 04 2018 at 18:01):
@Josh Mandel ?
Yunwei Wang (Apr 04 2018 at 18:02):
I find the same resource on smarthealthit.org itself.
https://sb-fhir-dstu2.smarthealthit.org/smartdstu2/data/metadata
Dan Gottlieb (Apr 04 2018 at 18:28):
@Yunwei Wang this is a bug in the version of HAPI that's underlying the sandbox (https://github.com/jamesagnew/hapi-fhir/issues/765 ). It should be fixed in the online sandbox when we upgrade to a more recent version of HAPI (currently targeted for the end of the April) and in the downloadable version when we move to a docker based release (targeted for this summer).
Yunwei Wang (Apr 04 2018 at 18:31):
@Dan Gottlieb Thank you for the confirmation. How I can manually remove that from conformance on my downloaded server?
Dan Gottlieb (Apr 04 2018 at 18:56):
@Travis Cummings since the SMART sandbox doesn't support the latest version of HAPI, is there an easy way for @Yunwei Wang to patch hapi-fhir-structures-dstu2/pom.xml locally without impacting the rest of the server or will that have to wait on updates to the SMART stack?
Travis Cummings (Apr 05 2018 at 19:57):
The way I would recommend installing a new version of HAPI to a SMART Installer deployment is:
1) on your server, change to the fhir user (sudo su fhir)
Travis Cummings (Apr 05 2018 at 19:58):
2) cd /home/fhir/api
Travis Cummings (Apr 05 2018 at 20:18):
3) expand the hspc-api jar file (I'm not able to expand it using "jar xf" for some reason, probably because of its executable packaging, so I used zip)
Travis Cummings (Apr 05 2018 at 20:19):
4) notice the Hapi Jars at BOOT-INF/lib
Travis Cummings (Apr 05 2018 at 20:20):
5) replace all of the Hapi jars with the version of Hapi you would like (ex: 3.3.0). make sure all of the Hapi jars are moved to the correct version, don't have a mix of Hapi jars.
Travis Cummings (Apr 05 2018 at 20:21):
6) Package up the hspc-api again
Travis Cummings (Apr 05 2018 at 20:22):
7) restart the api service using
Travis Cummings (Apr 05 2018 at 20:22):
sudo service api_dstu2 restart
Travis Cummings (Apr 05 2018 at 20:22):
sudo service api_stu3 restart
Travis Cummings (Apr 05 2018 at 20:24):
Alternative method (if you are set up for Java and Maven development):
1) clone the HSPC Reference API from https://bitbucket.org/hspconsortium/reference-api, master branch
Travis Cummings (Apr 05 2018 at 20:25):
2) update the ./pom.xml hapi.version property to be the version of Hapi you would like (ex: 3.3.0)
Travis Cummings (Apr 05 2018 at 20:27):
3) build the reference api as in the README.md, or "mvn clean install"
Travis Cummings (Apr 05 2018 at 20:29):
4) upload the jar from reference-api-webapp-multitenant/target to your SMART server at /home/fhir/api
Travis Cummings (Apr 05 2018 at 20:31):
5) alter the api services at /etc/systemd/system to point to the jar you just uploaded (there are 4 services, use "ls api_" to see them)
6) restart these 4 services
Travis Cummings (Apr 05 2018 at 20:38):
Whew, the final alternative is to ask @Nikolai Schwertner when HSPC will move to the Hapi 3.3.0 release. I would guess they could prioritize this at their 4/16/18 planning meeting, and release it as soon as 4/24/18 (assuming the schema is not changing).
Travis Cummings (Apr 05 2018 at 20:39):
In this scenario, the SMART installer would simply change the roles/api/defaults/main.yml property:
Travis Cummings (Apr 05 2018 at 20:39):
api_server_artifact_version: "1.11.7" becomes the next version of hspc's reference_api (ex: 1.14.0)
Travis Cummings (Apr 05 2018 at 20:42):
Then run the SMART installer's playbook_api.yml to install the newer version of the hspc artifact
Nikolai Schwertner (Apr 05 2018 at 20:49):
We will look into folding HAPI 3.3.0 into the HSPC sandbox
environment for 24 April 2018
Last updated: Apr 12 2022 at 19:14 UTC
