FHIR Chat · OpenMRS + keycloak integration · implementers

Stream: implementers

Topic: OpenMRS + keycloak integration


view this post on Zulip Servin Osmanov (Feb 14 2022 at 08:11):

Hi.
Can you help me integrate fhir into OpenMRS and keycloak using module fhir2 ?
I configured almost all, but all my requests returns error 500 Nullpointer.

view this post on Zulip Servin Osmanov (Feb 14 2022 at 08:13):

Environment:
MacOS
OpenMRS 2.4
keycloak 14
Fhir2 (openmrs-module-fhir2) 1.3.0
msrtonfhir (openmrs-module-smartonfhir) latest from github
keycloak-auth(https://github.com/openmrs/openmrs-contrib-keycloak-auth)
keycloak-smart-auth (https://github.com/openmrs/openmrs-contrib-keycloak-smart-auth)

Smart App configuration

{
  "id": "patient.monitor",
  "description": "patient.monitor",
  "order": 1,
  "config" : {
    "launchUrl" : "https://localhost/patient-monitor/launch.html",
    "launchType" : "EHR",
    "launchContext" : "patient",
    "fhirVersion" : "R4"
  },
  "extensions": [
    {
      "id": "smartapps.patientMonitorHomepageLink",
      "extensionPointId": "smartAppManagement.apps",
      "type": "link",
      "label": "patient.monitor",
      "url": "smartonfhir/smartAppsRedirect.page?app=patient.monitor",
      "icon": "icon-hdd",
      "requiredPrivilege": "App: smartonfhir.patientMonitorHomepageLink"
    }
  ]
}

keycloak realm configuration
realm-export.json

view this post on Zulip Grahame Grieve (Feb 14 2022 at 12:53):

@Burke Mamlin ?

view this post on Zulip Servin Osmanov (Feb 14 2022 at 13:29):

the problem is - getting error 500 on each requests. eg.
GET http://localhost:8080/openmrs/ws/fhir2/R4/Patient/3ca34181-1834-4ddb-aee8-88e1525e0870

<body>
    <h1>HTTP Status 500 – Internal Server Error</h1>
    <hr class="line" />
    <p><b>Type</b> Exception Report</p>
    <p><b>Description</b> The server encountered an unexpected condition that prevented it from fulfilling the request.
    </p>
    <p><b>Exception</b>
        <pre>java.lang.NullPointerException
</pre>
    </p>
    <p><b>Note</b> The full stack trace of the root cause is available in the server logs.</p>
    <hr class="line" />
    <h3>Apache Tomcat/7.0.94</h3>
</body>

Last updated: Apr 12 2022 at 19:14 UTC