These pages assist with requirements gathering and mapping stages of a FHIR API development process.
The Deploy section contains descriptions of approaches and suggestions for building APIs at the Assure stage.
The access mechanism and of requesting system is influenced by many factors. This section demonstrates the design decisions to consider
The security of the FHIR payload, access and data at rest are all important design decisions while building an API.
Please see or contribute to INTEROPen to support the wider community efforts of providing a completely defined API service.
Note: Provided as an overview
Providing an API
The following diagram explains the elements of APIs allowing a 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.
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 firstname.lastname@example.org or see more information at INTEROPen |