INTEROPen
These pages assist with requirements gathering and mapping stages of a FHIR API development process.
The Test section contains descriptions of approaches and suggestions for building APIs.
| Page | Description |
|---|---|
| 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. |
| Test Data | The test data allows the testing of the Care Connect APIs at the individual response level. |
Please see or contribute to INTEROPen to support the wider community efforts of providing a completely defined API service.
Note: This section provides an overview of the main elements of the testing process to consider within API development
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.
Contribute
This site is structured around Care Connect stakeholders including API users, developers and architects. Please get involved in the journey.