FHIR

RCKMS FHIR Service

Information on this page is likely out of date as of 2021-11-17.

Members of the HLN team will update this page after parallel production.

Overview

This is an implementation of a RESTful FHIR server, exposing RCKMS data as FHIR-structured resources, and uses a HAPI foundation.

Links and Resources

• GitHub Repository for HLN engineers/operators

• Mirrored GitHub Repository for AIMS read-only tag pulls

Environment Variables

Required

RCKMS FHIR service is dependent upon a functional Keycloak service.

• keycloak.auth-server-url string

  • Indicates the fully qualified URL (protocol, hostname, port, path) for the Keycloak service.

• keycloak.credentials.secret string

  • Sets the secret to authenticate with the Keycloak service.

• keycloak.ssl-required enum(string)

  • Sets the SSL connection tolerance for the Keycloak client.

  • Options include none, external requests, and all requests.

• mts-services.base-url string

  • Indicates the fully qualified URL (protocol, hostname, port, path) for MTS within the cluster.

• mts-services.core-service.username string

  • Indicates the username to use when connecting to MTS "Core" services.

• mts-services.core-service.password string

  • Indicates the password to use when connecting to MTS "Core" services.

Recommended

This service does not have any optional-but-recommended environment variables.

Optional

This service does not have any optional environment variables.

Resource Allocation & Availability

Recommended minimum quantity of pods per environment

Environment	Quantity
HLN Canary (staging)	1
HLN Training (training)	N/A
AIMS Sandbox (aims-sandbox)	TBD
AIMS Onboarding (aims-onboarding)	TBD
AIMS Production Readiness Review (aims-prr)	TBD
AIMS Production (aims-production)	TBD

Recommended minimum resource allocation per pod

CPU	CPU Intensive?	RAM	Storage	Preemptible?
750m	false	0.50Gi	N/A	true

• "CPU Intensive" indicates that this microservice is best served on a higher-class of compute resource, specifically intended for CPU intensive workloads. We recommend utilizing Kubernetes NodeAffinity requests to support this interaction.

• "Preemptible" indicates if a service can support operation atop lower-cost, ephemeral compute resources offered by a cloud platform (e.g. preemptible instances on GCP, spot instances on AWS). We recommend utilizing Kubernetes node taints to support this interaction.

Technology Stack

Container

• Java 11

Requests

Probes: Liveness

GET localhost:8080/manage/health

Refer to the Kubernetes Documentation for more information on probes.

204 Pod is ready to receive traffic.

{}

500 Pod is not ready to receive traffic.

{}

Probes: Readiness

GET localhost:8080/manage/health

Refer to the Kubernetes Documentation for more information on probes.

204 Pod is ready to receive traffic.

{}

500 Pod is not ready to receive traffic.

{}

Point-of-Contact / Code Owners

Name	Email
Blake Minghelli	[e-mail]