INTEROPen
Describes the steps required to design & build an API using the Care Connect profiles described in Explore
Important: All information provided below is indicative and subject to on-going review.
The Design & Build section contains descriptions of approaches and suggestions for building APIs.
| Page | Description |
|---|---|
| Design Patterns / Topology | Describes access patterns necessary which influence the access, security and use of APIs. Depending on the pattern or topology of the requesting and responding system. The relationship between the requestor and responder influences the choice of access mechanism, security of payload and access finally build of the system |
| Access | The access mechanism and of requesting system is influenced by many factors. This section demonstrates the design decisions to consider |
| Security | The security of the FHIR payload, access and data at rest are all important design decisions while building an API. |
| Build | A look at some tools and techniques to help build APIs using the Resources defined in Explore |
Please see or contribute to INTEROPen to support the wider community efforts of providing a completely defined API service.
Providing an API
The following diagram explains the elements of APIs allowing the development of APIs:
NHS Digital is contributing to progressing the profile development (see Overview section). Invitations are open for the INTEROPen community to get involved and progress the wider developer ecosystem as defined above.
Contribute
This site is structured around Care Connect stakeholders including API users, developers and architects. Please get involved in the journey.
Contribute: If you want to get involved with CareConnect APIs then please get in touch with apilabs@nhs.net or see more information at INTEROPen |