Skip to content

Conversation

@KazeemHamzat
Copy link
Collaborator

Updating SR for Trio Testing
Add CapabilityStatement element for RequestGroup (including read+search+parameters)
Create RequestGroup & GraphDefinition Resources

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)
Copy link
Contributor

@omarisgreat omarisgreat left a 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",
Copy link
Contributor

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",
Copy link
Contributor

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,
Copy link
Contributor

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

Copy link
Contributor

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",
Copy link
Contributor

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",
Copy link
Contributor

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"
Copy link
Contributor

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"
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants