"to" recipient Addressing checks

[kategill]

Part of 111 processing is for the receiver to check they can route the message to the right recipient. If a mistake is made in addressing fields (mapped into FHIR) and the receiver does not know who the recipient is then the message should be rejected. How is this done with the adaptor? The receiver should not process messages intended to recipients not on their service.

Note that the 111 sender end is expected to process rejections and check why sent incorrectly. Surely this process will now not be possible in this configuration?

The only way I can see this working synchronously is for the Adaptor to do this part, as the supplier is processing fhir transforms off the queue asynchronously. And so the adptor needs a list of addressees for that instance. In other words the supplier who takes the adaptor needs to maintain some reference info somewhere in the adaptor and be able to refresh that data frequently. Note the two addresses used are the ODS code and the DOS Service DI in the ITK header like this:
"

"
We've yet to work out accurately where these go in the FHIR as well - we need to!

[bartek-sarul]

@kategill do I understand correctly that you would like the adaptor

1. to have a configurable list of supported pairs of ODS + DOS Service DI(*) codes and those should be used in request handler to accept or reject a message?
2. to map those codes into FHIR ?

• what are DOS Service DI codes?

[dawidskainos]

Fixed in 0.8.0 release