Add a DICOM dataset to slicebox

What this operation does

add a DICOM dataset to slicebox

• POSTChanges data · Imagesslicebox.local/images

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Slicebox operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Slicebox operations

• Creates a new user. Dupicates are accepted but not addedPOST · changes data
• Add a new directory to watch for incoming DICOM filesPOST · changes data
• Add a new SCP for receiving DICOM imagesPOST · changes data
• Add a new SCU for sending DICOM imagesPOST · changes data
• Add a new series typePOST · changes data
• Obtain a session cookie that can be usedPOST · changes data
• Logout the current user by respondingPOST · changes data
• Create a new import sessionsPOST · changes data

All 118 Slicebox operations

Questions

Can HumDay add a dicom dataset to slicebox in Slicebox?

Yes. This operation is published in Slicebox's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Slicebox data?

Yes — this is a POST operation, so it changes something in Slicebox. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Slicebox account.

Where this came from

Read from a published API description for Slicebox at slicebox.github.io/slicebox-api/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.