To implement what is defined on the architecture, the ctr-backoffice-backend /borest/ctrms/submit needs to:
1 - if the duration of the rest of the operation takes many seconds, answer back to the patient-ssapp client some info that the MatchRequest has been submited. (During the development, as the number of trials is reduced, this might not need to be that way).
2 - match trials and create a MatchResult
3 - write the MatchResult to the blockchain
4 - notify the patient-ssapp that the MatchResult is available
Step 4 may just be a synchronous reply to /borest/ctrms/submit in low-volume trial scenario.
The scope of this issue is step 3: "write the MatchResult to the blockchain"
How to do that ?
a. call a REST service on apihub at 127.0.0.1 ?
b. invoke an external command-line tool ?
c. other ? Ask RMS.
To implement what is defined on the architecture, the ctr-backoffice-backend /borest/ctrms/submit needs to:
1 - if the duration of the rest of the operation takes many seconds, answer back to the patient-ssapp client some info that the MatchRequest has been submited. (During the development, as the number of trials is reduced, this might not need to be that way). 2 - match trials and create a MatchResult 3 - write the MatchResult to the blockchain 4 - notify the patient-ssapp that the MatchResult is available
Step 4 may just be a synchronous reply to /borest/ctrms/submit in low-volume trial scenario.
The scope of this issue is step 3: "write the MatchResult to the blockchain"
How to do that ?
a. call a REST service on apihub at 127.0.0.1 ? b. invoke an external command-line tool ? c. other ? Ask RMS.