Medtech ALEX® Implementation Guide
0.0.1 - draft
Medtech ALEX® Implementation Guide
0.0.1 - draft
Medtech ALEX® Implementation Guide - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.medtechglobal.com/CapabilityStatement/alexV1-0 | Version: 0.0.1 | |||
| Draft as of 2020-04-01 | Computable Name: MedtechCapabilityStatement | |||
This is the computable resource that describes the FHIR compliant RESTful endpoint exposed by the ALEX infrastructure
Note that all API interactions will be routed to a single Practice Management System as ALEX is effectively a facade layer in front of each PMS - ie it is not an aggregator accross different PMS systems. This means that if there is data about a single patient in different PMS’s then a call will be required to each one to retrieve all the data (assuming the client has the permission to do so). It is the responsibility of the client to perform any aggregation and de-duplication.
It is important that clients making API calls examine the resource type of all resources returned by a query - in particular the ALEX framework will add OperationOutcome resources in some calls - for example when a search returns no resources, ALEX will add an OperationOutcome resource to the Bundle to be explicit that there were no matching resources. (All queries will return a bundle - even if there were no matching resources).
Refer to the spec for details on using the API and search, though note that this API supports only a subset of the defined queries.
Raw OpenAPI-Swagger Definition file | Download