Capability Statement
LRA Server Capability Statement
This Capability Statement outlines the capabilities of the Longitudinal Record Access (LRA) Server, which is designed to support secure, standardized data exchange in healthcare. The LRA Server adheres to FHIR specifications and defines the resources, search parameters, interactions, and operations it supports. This statement ensures consistent implementation across healthcare systems, allowing for seamless integration and interoperability.
The LRA Server:
- Supports the following resources - Patient, Practitioner, Location, Organization and CoverageEligibilityResponse.
- Implements the RESTful behaviour according to the FHIR specification.
- Follows the requirements documented in the Conformance Requirements.
- Supports JSON, XML and ttl formats for all LRA interactions.
RESTful Capabilities by Resource
| Resource Type | Supported Searches | Supported Interactions | Supported Operations |
|---|---|---|---|
| Patient | identifier, family, given, address-city, address-country, address-line, address-postalcode, address-state, birthdate, death-date, email, gender, phone, _has | search-type, read, create, update | MergePatient, match |
| Practitioner (no RESTful capability, only Operation-based) | identifier, family, given, status, address-city, gender, role, communication, expertise, status-reason, with History | search-type, read | entityQuery |
| Location (no RESTful capability, only Operation-based) | identifier, name, address-city, address-line1, otheraddress-line1, healthAuthority, healthServiceDeliveryArea, localHealthArea, communityHealthServiceArea, primaryCareNetwork, withHistory | search-type, read | entityQuery |
| Organization (no RESTful capability, only Operation-based) | identifier, name, description, type, address-city, withHistory | search-type, read | entityQuery |
| CoverageEligibilityResponse | patient, serviced-date, _has | search-type |
Additional Notes:
- The LRA Server implements SMART on FHIR security, supporting OAuth 2.0 flows with tokens, introspection, and revocation URLs.
- Supported formats for LRA interactions include application/fhir+json and application/fhir+xml
- The
process-messageoperation is supported by the LRA server, enabling the handling of FHIR messaging scenarios, which is essential for event-based communications like coverage eligibility requests or clinical messaging workflows.