You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussed an alternative approach for returning questionnaireResponse resources with Martin.
Suggestion is to follow a similar pattern to returning them to the approach to returning related problems.
If an item returned in a query is part of a structure that would be related to a questionnaireResponse then the qR resource would be returned containing the links to the other related resources. It would not return the linked resources that are part of the structured area unless they were already part of the response to the query.
The approach would be different than the related problem header approach in that we will not define any further lists to be returned as part of the query.
Discussed with the clinicians and EMIS and have decided to remove questionnaireResponse from the specification. The structured data areas in which these occur only exist under a consultation heading which already provides some basic linkages. For the amount of effort and complication that this adds to the specification it adds little extra value.
It was introducing faked up heading which were confusing and the difficulty in how to return the QRs and what lists to use have made this an overcomplicated proposal. It was intended as a quick fix to offer data in a more structured way, however it was ending up as a somewhat half hearted solution for templates in EMIS. The clinical team agreed that it was better to spend morer time on templates that would create a better solution for all the suppliers
Add reference in the description for Uncategorised data and any additional related changes. Also may need to update Consultations description
The text was updated successfully, but these errors were encountered: