Risks

this month	last month	weeks on list	risk	risk resolution
1	1	5	FHIR data model changing	reviewing of new example FHIR bundle and agree the canonical version. Later, create some JSON validators that will specifically check that all required resources and fields are populated. Final option would be to have a gold standard report so that all data sources can ensure consistency of mapping from input form -> FHIR bundle.
3	-	=	GOSH deployment is on windows only	Ideally we'd have WSL2 enabled to allow for similar deployment as developement. Try and get a development virtual machine in August so that we can test deployment and rule out this risk
4	2	5	prototype used as production application	Allow for rounds of iteration when summer student starts and dedicate time to allowing edge cases to be worked on.
5	3	15	creeping requirements	review of requirements every 2 weeks, order by value and push down nice to haves until all high priority issues are completed
6	4	15	nothing useful released	agile development, constantly releasing usable code rather than goldplated. Would still like to have an end user of this to demo and get feedback from
7	5	15	released software has low quality	disciplined development practices (version control, review, tests and CI). End user sign off would be useful as well
8	6	15	no visibility on project progress	visible project board, write code in the open and under an open source license

Resolved risks:

this month	last month	weeks on list	risk	risk resolution
1	0	4	too much time spent on investigation	review work mid May to ensure a demo-able form with no frills
5	0	8	integration with fhir	straight to using fhir API rather than intermediate bundle which may not be correct