Notice
- Important: This guidance is under active development by NHS England and content may be added or updated on a regular basis.
- This Implementation Guide is currently in Draft and SHOULD NOT be used for development or active implementation without express direction from the NHS England Genomics Unit.
Unsolicited Reports
Within the Unified Genomic Record, there may be genomic reports which are either historic or are otherwise generated outside the Genomic Order Management service.
This results in reports which may not have the accompanying request context, including the rich clinical history, associated with a GOMS request.
For the UGR, a stubbed ServiceRequest is still expected, as this supports searching and visualisation, e.g. through NCRS, by structuring information normally provided as part of the request, such as the reason for testing. This information may only be in unstructured format in the report, which does not facilitate searching and categorisation.
The following resources are expected to be submitted as part of an Unsolicited Result submission to UGR. Each resource SHOULD conform to the minimal element cardinality and binding requirements set out within the profile pages in this Implementation Guide:
An example of an Unsolicited Report is provided on Bundle-UnsolicitedReport-Example.
Composition usage
The Pathology FHIR API implementation of a report expects a Document Bundle, with a Composition as focal resource. Whilst this guide uses a transaction based approach, to align with other Genomic Order Management operations, the UGR MAY make use of the Composition document operation to generate a Composition for submitted reports, and the associated Document bundles.
The Pathology standard also mandates the use of Provenance within the report bundle. This is not expected within the Genomics bundle as it is only required for routing within Pathology.