NHS North West Genomics
2.2.0 - ci-build
NHS North West Genomics - Local Development build (v2.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.nwgenomics.nhs.uk/Questionnaire/iGeneLaboratoryOrderExport | Version: 2.2.0 | ||||
| Draft as of 2026-09-20 | Computable Name: | ||||
Represents the flat-file shape of NEYctDNA.csv, iGene's daily CSV export of ctDNA
orders and reports copied to NE&Y Genomics for regional management information - see
ctDNA Management Information (NW to NE&Y
Genomics). One row per test; a report
row carries both order fields and report/result fields together, so this Questionnaire
models the full row - the order-only columns populate the FHIR Message O21 Laboratory
Order (Bundle-GenomicsOrderMessage-ctDNA),
while the report/result columns (ReportStatusDateTime, ReportIdentifier,
ObservationResultStatus, ObservationDateTime, ObservationIdentifierCode,
ObservationIdentifierDescription) instead populate the separate FHIR Message R01
Laboratory Report (Bundle-GenomicsReportMessage-ctDNA,
itself based on an HL7 v2 ORU^R01, not O21). See ctDNA Management Information -
Laboratory Order O21 Mapping
for the O21-only columns and Laboratory Report R01
Mapping for the
report/result columns - the two markdown tables split this Questionnaire's items by
which FHIR Message actually carries them, even though all items live on this one
Questionnaire. Named for iGene (the common source) rather than NE&Y/ctDNA
specifically, since the shape isn't NE&Y- or ctDNA-specific - it's the same LAB-2
CSV re-export pattern iGene Work Order Export
documents for StarLIMS/DLIMS work orders, just with ctDNA report/result columns added.
Each item's linkId is the literal CSV column header, type the FHIR datatype the
column's values coerce to, and definition the FHIR field the column populates once
converted into the relevant FHIR Message - many of these reuse the exact same field as
the equivalent item already defined on Genomic Test Order
or iGene Work Order Export, since
this is the same underlying order data plus report/result-specific columns those don't
carry. See NEYctDNA.csv
for the source file this was extracted from.
Unlike the Ask At Order Entry Questionnaires elsewhere in this IG, this is not a
derivedFrom/extends Questionnaire - it documents an existing system-to-system CSV
export shape, not a human-facing order-entry form.
Profile: Questionnaire
| LinkID | Text | Cardinality | Type | Description & Constraints![]() |
|---|---|---|---|---|
![]() |
Represents the flat-file shape of `NEYctDNA.csv`, iGene's daily CSV export of ctDNA orders and reports copied to NE&Y Genomics for regional management information - see [ctDNA Management Information (NW to NE&Y Genomics)](NEYManagementInformation.html#current-process). One row per test; a report row carries both order fields and report/result fields together, so this Questionnaire models the full row - the order-only columns populate the FHIR Message O21 Laboratory Order ([Bundle-GenomicsOrderMessage-ctDNA](Bundle-GenomicsOrderMessage-ctDNA.html)), while the report/result columns (`ReportStatusDateTime`, `ReportIdentifier`, `ObservationResultStatus`, `ObservationDateTime`, `ObservationIdentifierCode`, `ObservationIdentifierDescription`) instead populate the separate FHIR Message R01 Laboratory Report ([Bundle-GenomicsReportMessage-ctDNA](Bundle-GenomicsReportMessage-ctDNA.html), itself based on an HL7 v2 `ORU^R01`, not O21). See [ctDNA Management Information - Laboratory Order O21 Mapping](NEYManagementInformation.html#laboratory-order-o21-mapping) for the O21-only columns and [Laboratory Report R01 Mapping](NEYManagementInformation.html#laboratory-report-r01-mapping) for the report/result columns - the two markdown tables split this Questionnaire's items by which FHIR Message actually carries them, even though all items live on this one Questionnaire. Named for iGene (the common source) rather than NE&Y/ctDNA specifically, since the shape isn't NE&Y- or ctDNA-specific - it's the same LAB-2 CSV re-export pattern [iGene Work Order Export](Questionnaire-iGeneWorkOrderExport.html) documents for StarLIMS/DLIMS work orders, just with ctDNA report/result columns added. Each item's `linkId` is the literal CSV column header, `type` the FHIR datatype the column's values coerce to, and `definition` the FHIR field the column populates once converted into the relevant FHIR Message - many of these reuse the exact same field as the equivalent item already defined on [Genomic Test Order](Questionnaire-GenomicTestOrder.html) or [iGene Work Order Export](Questionnaire-iGeneWorkOrderExport.html), since this is the same underlying order data plus report/result-specific columns those don't carry. See [NEYctDNA.csv](https://github.com/nw-gmsa/Testing/blob/main/Input/NEYctDNA.csv) for the source file this was extracted from. Unlike the Ask At Order Entry Questionnaires elsewhere in this IG, this is not a `derivedFrom`/`extends` Questionnaire - it documents an existing system-to-system CSV export shape, not a human-facing order-entry form. | Questionnaire | https://fhir.nwgenomics.nhs.uk/Questionnaire/iGeneLaboratoryOrderExport#2.2.0 | |
![]() ![]() |
Patient | 0..1 | group | Definition: Patient Value Set: |
![]() ![]() ![]() |
PatientAccessionIdentifier | 0..1 | string | Definition: Patient.identifier:PatientIdentifier Value Set: |
![]() ![]() ![]() |
NHSNumber | 0..1 | string | Definition: Patient.identifier:nhsNumber Value Set: |
![]() ![]() ![]() |
HospitalNumber | 0..1 | string | Definition: Patient.identifier:MedicalRecordNumber Value Set: |
![]() ![]() ![]() |
PatientFamilyName | 0..1 | string | Definition: Patient.name.family Value Set: |
![]() ![]() ![]() |
PatientGivenName | 0..1 | string | Definition: Patient.name.given Value Set: |
![]() ![]() ![]() |
DateOfBirth | 0..1 | date | Definition: Patient.birthDate Value Set: |
![]() ![]() ![]() |
AdministrativeSex | 0..1 | string | Definition: Patient.gender Value Set: |
![]() ![]() ![]() |
PostCode | 0..1 | string | Definition: Patient.address.postalCode Value Set: |
![]() ![]() |
Healthcare Professional | 0..1 | group | Definition: PractitionerRole Value Set: |
![]() ![]() ![]() |
OrderingProviderIdentifier | 0..1 | string | Definition: PractitionerRole.practitioner.identifier.value Value Set: |
![]() ![]() ![]() |
OrderingProviderName | 0..1 | string | Definition: PractitionerRole.practitioner.display Value Set: |
![]() ![]() ![]() |
RequestingOrganisationCode | 0..1 | string | Definition: PractitionerRole.organization.identifier.value Value Set: |
![]() ![]() ![]() |
RequestingOrganisationName | 0..1 | string | Definition: PractitionerRole.organization.display Value Set: |
![]() ![]() |
Test Request | 0..1 | group | Definition: ServiceRequest Value Set: |
![]() ![]() ![]() |
HospitalSpellIdentifier | 0..1 | string | Definition: ServiceRequest.encounter.identifier Value Set: |
![]() ![]() ![]() |
PlacerOrderNumber | 0..1 | string | Definition: ServiceRequest.identifier:OrderIdentifier Value Set: |
![]() ![]() ![]() ![]() |
identifier.type = PLAC (v2-0203), the same OrderIdentifier slice FillerOrderNumber below uses with type = FILL. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
FMIIdentifier | 0..1 | string | Definition: ServiceRequest.identifier Value Set: |
![]() ![]() ![]() ![]() |
Blank on every current example row - purpose and identifier system not yet confirmed. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
FillerOrderNumber | 0..1 | string | Definition: ServiceRequest.identifier:OrderIdentifier Value Set: |
![]() ![]() ![]() ![]() |
identifier.type = FILL (v2-0203). | 0..1 | display | Value Set: |
![]() ![]() ![]() |
OrderStatus | 0..1 | string | Definition: ServiceRequest.status Value Set: |
![]() ![]() ![]() |
NGTDTestCode | 0..1 | string | Definition: ServiceRequest.code Value Set: |
![]() ![]() ![]() |
NGTDTestName | 0..1 | string | Definition: ServiceRequest.code.coding.display Value Set: |
![]() ![]() ![]() |
TestCode | 0..1 | string | Definition: ServiceRequest.code.coding Value Set: |
![]() ![]() ![]() ![]() |
A shorter local iGene test code (e.g. ctDNA_M4) alongside the national NGTDTestCode - a second `coding` entry on the same ServiceRequest.code, local system not yet confirmed. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
TestAccessionIdentifier | 0..1 | string | Definition: ServiceRequest.identifier Value Set: |
![]() ![]() ![]() ![]() |
A further, test-level iGene identifier distinct from both the Placer and Filler Order Number slices above - exact identifier.type/system not yet confirmed. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
TestOrderDate | 0..1 | dateTime | Definition: ServiceRequest.authoredOn Value Set: |
![]() ![]() |
Report | 0..1 | group | Definition: DiagnosticReport Value Set: |
![]() ![]() ![]() |
ReportStatusDateTime | 0..1 | dateTime | Definition: DiagnosticReport.issued Value Set: |
![]() ![]() ![]() |
ReportIdentifier | 0..1 | string | Definition: DiagnosticReport.identifier:ReportIdentifier Value Set: |
![]() ![]() ![]() |
ObservationResultStatus | 0..1 | string | Definition: DiagnosticReport.status Value Set: |
![]() ![]() ![]() ![]() |
F = finalised - see Why this matters for developers on NEYManagementInformation.html for how this drives treating an R01 copy as a completed test. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
ObservationDateTime | 0..1 | dateTime | Definition: DiagnosticReport.effectiveDateTime Value Set: |
![]() ![]() ![]() ![]() |
Populated on DiagnosticReport.effectiveDateTime in the current worked example - see R01 Mapping on NEYManagementInformation.html for detail, including why this isn't the individual result Observation's own effectiveDateTime. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
ObservationIdentifierCode | 0..1 | string | Definition: DiagnosticReport.conclusionCode.coding:GenomicTestOutcomeCode.code Value Set: |
![]() ![]() ![]() ![]() |
Also known as the Genomics Test Outcome - see Genomic Test Outcome Codes and R01 Mapping on NEYManagementInformation.html for detail. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
ObservationIdentifierDescription | 0..1 | string | Definition: DiagnosticReport.conclusionCode.coding:GenomicTestOutcomeCode.display Value Set: |
![]() ![]() |
Specimen/Biopsy | 0..1 | group | Definition: Specimen Value Set: |
![]() ![]() ![]() |
SpecimenTakenDateTime | 0..1 | dateTime | Definition: Specimen.collection.collectedDateTime Value Set: |
![]() ![]() ![]() |
SpecimenReceivedDateTime | 0..1 | dateTime | Definition: Specimen.receivedTime Value Set: |
![]() ![]() ![]() |
SpecimenAccessionIdentifier | 0..1 | string | Definition: Specimen.accessionIdentifier Value Set: |
![]() ![]() ![]() |
SpecimenTypeCode | 0..1 | string | Definition: Specimen.type.coding.code Value Set: |
![]() ![]() ![]() ![]() |
Normally SNOMED coded using the [Specimen Type](ValueSet-specimen-type.html) value set. | 0..1 | display | Value Set: |
![]() ![]() ![]() |
SpecimenTypeDescription | 0..1 | string | Definition: Specimen.type.coding.display Value Set: |
Documentation for this format | ||||
Profile: Questionnaire
Patient
PatientAccessionIdentifier
NHSNumber
HospitalNumber
PatientFamilyName
PatientGivenName
DateOfBirth
AdministrativeSex
PostCode
Healthcare Professional
OrderingProviderIdentifier
OrderingProviderName
RequestingOrganisationCode
RequestingOrganisationName
Test Request
HospitalSpellIdentifier
PlacerOrderNumber
identifier.type = PLAC (v2-0203), the same OrderIdentifier slice FillerOrderNumber below uses with type = FILL.
FMIIdentifier
Blank on every current example row - purpose and identifier system not yet confirmed.
FillerOrderNumber
identifier.type = FILL (v2-0203).
OrderStatus
NGTDTestCode
NGTDTestName
TestCode
A shorter local iGene test code (e.g. ctDNA_M4) alongside the national NGTDTestCode - a second `coding` entry on the same ServiceRequest.code, local system not yet confirmed.
TestAccessionIdentifier
A further, test-level iGene identifier distinct from both the Placer and Filler Order Number slices above - exact identifier.type/system not yet confirmed.
TestOrderDate
Report
ReportStatusDateTime
ReportIdentifier
ObservationResultStatus
F = finalised - see Why this matters for developers on NEYManagementInformation.html for how this drives treating an R01 copy as a completed test.
ObservationDateTime
Populated on DiagnosticReport.effectiveDateTime in the current worked example - see R01 Mapping on NEYManagementInformation.html for detail, including why this isn't the individual result Observation's own effectiveDateTime.
ObservationIdentifierCode
Also known as the Genomics Test Outcome - see Genomic Test Outcome Codes and R01 Mapping on NEYManagementInformation.html for detail.
ObservationIdentifierDescription
Specimen/Biopsy
SpecimenTakenDateTime
SpecimenReceivedDateTime
SpecimenAccessionIdentifier
SpecimenTypeCode
Normally SNOMED coded using the [Specimen Type](ValueSet-specimen-type.html) value set.
SpecimenTypeDescription
Profile: Questionnaire
| LinkID | Description & Constraints![]() |
|---|---|
![]() |
Definition: Patient Value Set: |
![]() ![]() |
Definition: Patient.identifier:PatientIdentifier Value Set: |
![]() ![]() |
Definition: Patient.identifier:nhsNumber Value Set: |
![]() ![]() |
Definition: Patient.identifier:MedicalRecordNumber Value Set: |
![]() ![]() |
Definition: Patient.name.family Value Set: |
![]() ![]() |
Definition: Patient.name.given Value Set: |
![]() ![]() |
Definition: Patient.birthDate Value Set: |
![]() ![]() |
Definition: Patient.gender Value Set: |
![]() ![]() |
Definition: Patient.address.postalCode Value Set: |
![]() |
Definition: PractitionerRole Value Set: |
![]() ![]() |
Definition: PractitionerRole.practitioner.identifier.value Value Set: |
![]() ![]() |
Definition: PractitionerRole.practitioner.display Value Set: |
![]() ![]() |
Definition: PractitionerRole.organization.identifier.value Value Set: |
![]() ![]() |
Definition: PractitionerRole.organization.display Value Set: |
![]() |
Definition: ServiceRequest Value Set: |
![]() ![]() |
Definition: ServiceRequest.encounter.identifier Value Set: |
![]() ![]() |
Definition: ServiceRequest.identifier:OrderIdentifier Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: ServiceRequest.identifier Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: ServiceRequest.identifier:OrderIdentifier Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: ServiceRequest.status Value Set: |
![]() ![]() |
Definition: ServiceRequest.code Value Set: |
![]() ![]() |
Definition: ServiceRequest.code.coding.display Value Set: |
![]() ![]() |
Definition: ServiceRequest.code.coding Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: ServiceRequest.identifier Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: ServiceRequest.authoredOn Value Set: |
![]() |
Definition: DiagnosticReport Value Set: |
![]() ![]() |
Definition: DiagnosticReport.issued Value Set: |
![]() ![]() |
Definition: DiagnosticReport.identifier:ReportIdentifier Value Set: |
![]() ![]() |
Definition: DiagnosticReport.status Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: DiagnosticReport.effectiveDateTime Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: DiagnosticReport.conclusionCode.coding:GenomicTestOutcomeCode.code Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: DiagnosticReport.conclusionCode.coding:GenomicTestOutcomeCode.display Value Set: |
![]() |
Definition: Specimen Value Set: |
![]() ![]() |
Definition: Specimen.collection.collectedDateTime Value Set: |
![]() ![]() |
Definition: Specimen.receivedTime Value Set: |
![]() ![]() |
Definition: Specimen.accessionIdentifier Value Set: |
![]() ![]() |
Definition: Specimen.type.coding.code Value Set: |
![]() ![]() ![]() |
Value Set: |
![]() ![]() |
Definition: Specimen.type.coding.display Value Set: |
Documentation for this format | |
Try this questionnaire out:
There are currently no QuestionnaireResponse instances for this Questionnaire defined in this IG.