MONAI Deploy Application Server

[pritishnahar95]

This PR adds a draft of the MONAI Deploy App Server specification.

This contains a description of the initial set of requirements and design for MONAI Deploy App Server.

[whoisj]

/CC @KarthikMasi @bhatt-piyush to review and provide feedback.

[ristoh]

This PR adds a draft of the MONAI Deploy App Server specification.

This contains a description of the initial set of requirements for MONAI Deploy App Server.

This PR does not include any design or implementation. These will be made available in future PRs.

Similar comments for this as for the MAP PR #7 :

We need to decide if this is a Guideline or Feature, in case this is a feature I'll propose the following changes on this:

change the branch name to be:

• feature/4-app-server
• make the feature specification available in folder features/app-server.md

cc @hshuaib90

[hshuaib90]

This PR adds a draft of the MONAI Deploy App Server specification.
This contains a description of the initial set of requirements for MONAI Deploy App Server.
This PR does not include any design or implementation. These will be made available in future PRs.

Similar comments for this as for the MAP PR #7 :

We need to decide if this is a Guideline or Feature, in case this is a feature I'll propose the following changes on this:

change the branch name to be:

• feature/4-app-server
• make the feature specification available in folder features/app-server.md

cc @hshuaib90

Similar to comment I made for #7, the primary output of this PR is a document rather than code and as such it should be classified as Guideline.

[whoisj]

@ristoh @hshuaib90 please see my comment on #7 as well. I think we're heading down the wrong path here.

[hshuaib90]

These requirements are a good start but I do not think they cover the requirements we have already discussed in our WG meetings. I think we should at least cover those in 0.1 release.

I would also propose amending the document name to MONAI-App-Server-Requirements.md

[whoisj]

@hshuaib90 can you expand on your statement?

These requirements are a good start but I do not think they cover the requirements we have already discussed in our WG meetings.

[hshuaib90]

@hshuaib90 can you expand on your statement?

These requirements are a good start but I do not think they cover the requirements we have already discussed in our WG meetings.

For example, we have discussed the requirement to have the ability to execute nondeterministic chains or DAGs made up of individual applications, as well was things like facilitating the sending of results to clinical information systems such as Picture Archiving and Communication Systems. There is a helpful diagram that Jorge added here: https://docs.google.com/document/d/1fzG3z7TxB9SzWdfqsApAMFrM91nHfYiISnSz4QHJHrM/edit#heading=h.677zfo5wg7au

[whoisj]

For example, we have discussed the requirement to have the ability to execute nondeterministic chains or DAGs made up of individual applications

While that has been a discussion point, I feel it is well outside the scope of the initial version of the Application Server. Functionality such as this would require a much more elaborate specification, design, and investment than we can likely make with the initial version.

as well was things like facilitating the sending of results to clinical information systems such as Picture Archiving and Communication Systems.

Again, outside the scope of the Application Server. The goal of the Application Server is to serve applications on demand based on requests from external entities (PACS, users, etc.). What you're describing here sounds very much like the "infomatics gateway" @rahul-imaging describes, which is a separate service which sits along side the Application Server.

Please let me know if I am making sense, or (likely) not quite understanding something and missing the point. 🙂

[whoisj]

I like the diagrams you've added, but as a point of discussion with the WG in general: do we prefer to see sequence diagrams in the format currently in the PR, or would we prefer more traditional sequence diagrams. Examples below:

[whoisj]

We discussed via Teams a few select changes, mostly around making everything into bullet points or numbered lists. Assuming those changes are made, I'm good with this.