[X] Add a link to the related issue at the top of this description (above)
[X] Connect this PR with the related issue via ZenHub with the button below this text box (or at the bottom of the page after the PR is created)
[X] Ensure your branch is up to date with the target branch and resolve any conflicts
[X] Answer the below questions to describe your PR for reviewers
[X] Request at least two reviewers using the "Reviewers" section on the right, usually including at least one reviewer from your team
[X] Notify the requested reviewers in the #code-review Slack channel once the PR is ready for review
Why are these changes needed?
Due to the latest redesign, which introduced a bootstrapped version of UI components, creating the Diagnostic Report component was necessary to fulfill the requirements.
What changed?
How are these changes tested?
All automatic tests are passing
The DiagnosticReport component might be tested manually by viewing the current version of the deployed storybook
Issue: PATIENTAPP-55
PR Checklist
Why are these changes needed?
Due to the latest redesign, which introduced a bootstrapped version of UI components, creating the Diagnostic Report component was necessary to fulfill the requirements.
What changed?
How are these changes tested?