Documentation
¶
Overview ¶
Package shngateway is the root of the shn-gateway module — the public, partner-deployable Smart Gateway engine. The engine lives in ./engine, its reference FHIR connector in ./connectors/fhirsor, and its private FHIR client in ./internal/fhirclient. It depends only on github.com/SmartHealthNetwork/shn-sdk.
Directories
¶
| Path | Synopsis |
|---|---|
|
Package app is the federation-capable PUBLIC gateway runtime.
|
Package app is the federation-capable PUBLIC gateway runtime. |
|
cmd
|
|
|
gateway
command
Binary gateway is the PUBLIC, federation-capable Smart Gateway: it boots config-only, loads its `shn register` bundle, federates against the live /discovery + the registrar feed, and runs prior auth for its ROLE.
|
Binary gateway is the PUBLIC, federation-capable Smart Gateway: it boots config-only, loads its `shn register` bundle, federates against the live /discovery + the registrar feed, and runs prior auth for its ROLE. |
|
connectors
|
|
|
fhirsor
Package fhirsor implements engine.SystemOfRecord by reading a US Core FHIR server (via internal/fhirclient).
|
Package fhirsor implements engine.SystemOfRecord by reading a US Core FHIR server (via internal/fhirclient). |
|
pgstore
Package pgstore is the durable (Postgres) implementation of the gateway's Store seam — the holder's OWN business state: issued authorization numbers, the pended-claim ledger, and PA-decision EOBs (AI-1: metadata/decision only, never a cross-holder clinical record).
|
Package pgstore is the durable (Postgres) implementation of the gateway's Store seam — the holder's OWN business state: issued authorization numbers, the pended-claim ledger, and PA-decision EOBs (AI-1: metadata/decision only, never a cross-holder clinical record). |
|
scaffold
Package scaffold is a runnable Tier-3 starter for partners whose backend is NOT a FHIR server (HL7v2, X12, SQL, SOAP).
|
Package scaffold is a runnable Tier-3 starter for partners whose backend is NOT a FHIR server (HL7v2, X12, SQL, SOAP). |
|
smartauth
Package smartauth lets a gateway authenticate to its FHIR data server via SMART Backend Services (RFC 7523 signed-JWT client-credentials).
|
Package smartauth lets a gateway authenticate to its FHIR data server via SMART Backend Services (RFC 7523 signed-JWT client-credentials). |
|
Package gateway is the Smart Gateway: the holder-side integration point that composes identity, per-operation authorization, payload-blind envelopes, FHIR mapping, and per-message profile validation.
|
Package gateway is the Smart Gateway: the holder-side integration point that composes identity, per-operation authorization, payload-blind envelopes, FHIR mapping, and per-message profile validation. |
|
internal
|
|
|
fhirclient
Package fhirclient is a small read-only FHIR R4 HTTP client (Search and Read).
|
Package fhirclient is a small read-only FHIR R4 HTTP client (Search and Read). |
Click to show internal directories.
Click to hide internal directories.