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
Monai is set up for on-premise execution of Argo workflows, App developers seem to operate on the principle that their apps are hosted in a centralized off-premise location under their control.
Mig allows plugins which would allow psdonymisation of the data outbound and rehydration inbound, which contributes towards the solution.
A number of changes are required to allow the Mig to re-identify data inbound (from one of these apps) so that it knows the difference between a new study inbound and a returning one (workflowInstanceId and TaskId are needed for returning ones)
The outbound studyInstanceId could be changed to a new value and data stored against that, on the inbound this would be used to reidentify the data.
A new port should be used to clearer separate new studies and returning ones.
The same ReIdentifing procedure (along side some new HL7 config) could be used to support HL7 messages inbound.
The text was updated successfully, but these errors were encountered:
Monai is set up for on-premise execution of Argo workflows, App developers seem to operate on the principle that their apps are hosted in a centralized off-premise location under their control.
Mig allows plugins which would allow psdonymisation of the data outbound and rehydration inbound, which contributes towards the solution.
A number of changes are required to allow the Mig to re-identify data inbound (from one of these apps) so that it knows the difference between a new study inbound and a returning one (workflowInstanceId and TaskId are needed for returning ones)
The outbound studyInstanceId could be changed to a new value and data stored against that, on the inbound this would be used to reidentify the data.
A new port should be used to clearer separate new studies and returning ones.
The same ReIdentifing procedure (along side some new HL7 config) could be used to support HL7 messages inbound.
The text was updated successfully, but these errors were encountered: