A proof of concept is a preliminary demonstration of the system's feasibility, functionality and potential value. It exists to answer questions cheaply that would otherwise be answered expensively.
- Define objectives. Validate technical feasibility, assess user acceptance, or demonstrate specific capability.
- Identify use cases. Emergency patient triage, blood product management, incident reporting or interoperability.
- Design system architecture. Components, technologies, integration points and stakeholder roles.
- Data modelling and integration. Data models incorporating FHIR resources and ledger structures; connections established to BBIMS and A&E systems.
- Develop prototype. A functional minimum viable product covering core A&E management, ledger and interoperability capability.
- Implement blockchain components. Smart contracts, distributed ledger, consensus, immutability, access controls and audit trails.
- Conduct testing. Unit, integration and user acceptance testing for functionality, performance and security.
- Gather feedback. From healthcare providers, emergency responders and administrators on usability and enhancement.
- Evaluate results. Against the predefined objectives and success criteria — feasibility, scalability, value proposition.
- Document learnings. Findings, challenges, opportunities and recommendations to inform further development.
A proof of concept is the sensible first commitment
It establishes whether the approach works in your environment before either party commits to a full implementation.