Client Registry Implementation Guide
0.1.0 - ci-build
Client Registry Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://ig.hiu.lk/fhir/clientregistry/CapabilityStatement/lk-client-registry-capability-statement | Version: 0.1.0 | |||
| Draft as of 2026-12-31 | Computable Name: LK_ClientRegistry_CapabilityStatement | |||
This capability statement describes the interactions that are supported by the Client Registry.
Raw OpenAPI-Swagger Definition file | Download
jsonNote to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
serverThe Client Registry supports a limited number of interactions and has special operations.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | V-R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|---|
| Patient | http://ig.hiu.lk/fhir/clientregistry/StructureDefinition/LKPatient | y | y | y | y | y | _id, active, gender, birthdate, family, given, telecom, identifier | none | none | $getIdentifierList, $linkClients |
read, vread, update, search-type, create.| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | _id | string | |
| SHALL | active | token | |
| SHALL | gender | token | |
| SHALL | birthdate | date | |
| SHALL | family | string | |
| SHALL | given | string | |
| SHALL | telecom | token | |
| SHALL | identifier | token |
| Conformance | Operation | Documentation |
|---|---|---|
| SHALL | $getIdentifierList | Request for a list of identifiers (across source systems) for a particular Client. |
| SHALL | $linkClients | This operation is used to link two Clients. Linking is an internal procedure where the system applies some confirmation and 'links' resource instances with an internal mechanism. The 'link' is not disclosed or part of any FHIR resource, but a user can confirm the linkage by searching with the identifier list operation. |