-
Notifications
You must be signed in to change notification settings - Fork 1
Feature-IOPS-4026-Remodelling Duo Trio Genomic tests #193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Feature-IOPS-4026-Remodelling Duo Trio Genomic tests #193
Conversation
KazeemHamzat
commented
Jan 14, 2026
Updating the SR to create for family members and linked them with a Req. ID
Correction to canonical URL of the codesystem
Create RequestGroup & GraphDefinition Resources for grouping orders, retrieving order and result
Add CapabilityStatement element for RequestGroup (including read+search+parameters)
omarisgreat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor changes requested, looking good
| "type": "token" | ||
| }, | ||
| { | ||
| "name": "subject", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know subject is used for other resource types but would it be possible to replace this with patient (across any resource type which has patient as a search parameter?
| "type": "date" | ||
| }, | ||
| { | ||
| "name": "intent", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure this is needed but happy to leave in for now
| }, | ||
| { | ||
| "description": "Other ServiceRequests in the trio with the same requisition identifier", | ||
| "min": 2, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be 0 if only the proband has been added so far
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For both the graphdefinitions, could you check the equivalent graphdefinitions for the individual service request to ensure they all the links are included, e.g. specimens referencing the request?
| "max": "*", | ||
| "target": [ | ||
| { | ||
| "type": "ServiceRequest", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will also need to follow links from all linked service requests so you may need sub links for the information referenced from the additionally retrieved requests
| "authoredOn": "2026-01-13T12:00:00Z", | ||
| "action": [ | ||
| { | ||
| "title": "Proband Genomic Test", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might need to remove this as there won't be information in the individual service requests to populate this field automatically, unless you replace the title with the identifier for the request (probably under action.resource.identifier)
| ], | ||
| "supportingInfo": [ | ||
| { | ||
| "reference": "Patient/Patient-PheobeSmithamFather-Example" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can remove this as it is now captured under this request subject
| ], | ||
| "supportingInfo": [ | ||
| { | ||
| "reference": "Patient/Patient-PheobeSmithamMother-Example" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, can remove patient in supporting info