Approach to Engagement
This process lays down steps of engagement with the client to analyse their business requirements for interoperability in a way that it supports mapping your requirements to CareConnect Profiles (that user HL7 INTEROPen FHIR standards) and enable the development of a live API (Application Programming Interface) to read or exchange information/data.
It has been cited that it’s very difficult to exchange information between various business units in health care sector as most of them follow their own data structures to exchange information. This causes lot of interoperability issues and rework. Implementing this process gives us the opportunity to demonstrate and guide the business units as to how these issues can be resolved using standards- FHIR (Fast Health Information Resources) and Care Connect Profiles which adhere to interoperability standards defined by INTEROPen community (INTEROPen.org). A standardised approach will provide a common language for engagement and will more easily support a framework for sharing knowledge that can continue to assist future projects and possibly become self sustaining within the community.
Business Benefit
This process will add business value by enabling businesses to easily exchange information in a common format as defined by FHIR and Profiles which is easily understood by rest of the organisation.
The Process
The process is broken down into 15 discrete steps that are broadly organised onto three stages: Agree Business Requirements, Define the Solution, and Deliver the Solution.
Agree Business Requirements
| Step | Description | Formal Output | |
|---|---|---|---|
| 1 | Document Client's Context | Give a brief description of the client we are engaging with and what led them to the business need for interoperability. |
|
| 2 | Document Case Overview | Description of the client's business needs and expectations. |
|
| 3 | Document Problem Statement | Describe the current ineroperability issues. |
|
| 4 | Identify Business Requirements | Visually represent the business case to confirm understanding of the problem with the client. |
|
| 5 | Identify Dataset | Given that the solution is likely to be implemented against existing systems it should be straightforward to identify which data items the client wants to send or receive between those systems. Get XML representation of the data structure if possible. |
|
Define the Solution
| Step | Description | Formal Output | |
|---|---|---|---|
| 6 | Identify Care Connect Profiles and FHIR Resources | Identify which Care Connect profiles and FHIR resources can be used to meet the requirement. An entity relationship diagram can help to describe the profiles. |
|
| 7 | Map Dataset | Map the dataset to the profile. |
|
| 8 | Obtain Approval | Get Profile to Dataset Mapping reviewed and approved by the client. | |
| 9 | Design API | Define API Signatures and use of Search Parameters |
|
| 10 | Document Interaction Flow | Define the sequence of interactions expected including the function, input parameters, output parameters etc. |
|
| 11 | Document Additional Technical Context | Identify any further technical considerations to aid understanding. |
|
| 12 | Resolve Curation Requirements | Feedback to INTEROPen any necessary changes to Profile definitions. |
|
Deliver the Solution
| Step | Description | Formal Output | |
|---|---|---|---|
| 13 | Present Case Study | Present final case study to stakeholders and include it into the implementation guide. |
|
| 14 | Implement Solution | Client implements solution, tests and provides feedback. | |
| 15 | Learning | Identify failures and successes of the project. |
|