In diag 5 the RDT lists are eliminated, instead they can be displayed via the evaluation search. In the evaluation search there are two filter set templates for this purpose, which can be adapted to the customer's needs.
The incoming lists can be monitored with the status button.
The head office operates passively and only the senders upload and download the evaluations. The head office itself only makes the reports available for download, but does not send anything itself.
First the public URL must be set up in the head office, this can be done manually, see screenshot, or by automatic configuration using the Dynamic URL and SSL. item. This system maps the dynamic IP address to a fixed URL and at the same time secures the connection with an SSL certificate
A doctor is created in the central office for each sender and then a setup file is created for this doctor. With this setup file the sender can then configure his channels.
First a new doctor must be created
A setup file is then created for this doctor. You can see the doctor is always in the state "Unregistered".
First open a either the Internet Explorer or the MS Edge browser on the server where the custo diagnostic server is installed and open the following web pages:
https://kybe.customed.de/CustoCentral/ (Error 404 will appear, but's ok)
and
In case any of the SSL certificates on those web pages should be considered as untrusted please get the untrusted one stored in the computer certificate store.
Then go to the services.mmc and restart the Appache Tomcat server.
Go back to the service center:
The client now imports this configuration file under "Client Configuration" → "Add Channel".
Here should be selected a meaningful name for the output channel, so that the sender knows to whom he later sends the evaluation.
By confirming the dialog, the system automatically checks whether the connection to the central office is possible. If the connection was successful, the status of the doctor in the central unit goes to "Online Exchange" and dial-up is configured.
| Zusender | Zentrale |
|---|---|
|
|
The configuration of the status button is is explained here
The standard default for the evaluation set in the Central is "RDT Central Worklist". This search maps all evaluation types that are typically considered for EDI and also sets the flag for "not found" and the EDI flag "Incoming", i.e. all evaluations that have arrived in the central office but have not yet been viewed.
If this filter set is too extensive, it can be modified at any time and saved as a new set.
The activated hints of the status button should then either point to the basic filter set, or to the modified one, so that the user in the control center can immediately see when a new evaluation has come in, which he should find.
The same applies to the sender. The standard set "RDT Client Worklist" is available here.
This set maps all evaluations that have been received back from the head office. You should adjust this set according to the sender's workflow, otherwise the list will continue to grow.
are proposals:
| Workflow | Proposal for input filter set | |
|---|---|---|
| Sender always prints evaluation | Add status: "Printed no" | |
| Sender always exports evaluation | Add status: "Exported No | |
| Sender only looks at returned evaluation | Set option to change flag. When the evaluation is closed, the flag is changed to RECEIVED_AND_FINISHED and these evaluations no longer appear in the standard filter set
|
What does that mean? | Where does it appear? | How can I fix it? |
|---|---|---|
Fehler MISSING_END
| Service-Center Status page (Central / Client) | This error occurs if the evaluation is open and therefore cannot be downloaded by the sender. Remedy: Close and wait for the server to download the evaluation sent by EDI at the client. |
