Segregating MWL patients fetched by machines

[Aryan Sri]

I've connected my DCM4CHEE PACS with OHIF viewer and platform built around it. Now, while creating a patient, it is only shown to that particular hospital on the platform, but when we make an appointment for the patient, it creates an MWL entry for the patient in the DCM4CHEE, which can be fetched by a scanning machine to do the scans. Now, while this flow is working fine, the WORKLIST containing scheduled appointments or MWL is fetching all the patient appointments from all the hospitals. So, when a machine in hospital X fetches the data, it can see the MWL created by hospitals Y and Z as well, and can access information about those patients. MWL API is fetching all the data from the WORKLIST. Is there a way we can solve this?

[fleetwoodfc]

Yes you can use Archive Attribute Coercion

[Vrinda Nayak]

Which version of the archive are you using and how was the MWL created - using HL7 order messages or REST API?

Version 5.30.0 onwards, WorklistLabel (0074,1202) can be used to segregate the worklists per tenants / hospitals. You need to ensure the corresponding configurations are present whereby each tenant / hospital can send HL7 order messages / invoke REST API to create MWL using specific endpoints on archive. Default configuration of archive does not have this feature and all modality worklists get WorklistLabel assigned as * which can be query / retrieved by any client