Create a RegistryPackage ebXML object to represent the SubmissionSet, assigning a globally unique entryUUID (urn:uuid:…) and populating uniqueId, sourceId, submissionTime, patientId, contentTypeCode, and title
For each document being submitted, create an ExtrinsicObject with its own entryUUID, uniqueId, mimeType, and all required document metadata slots
Link each document to the SubmissionSet by creating a Classification object of type HasMember and an Association of type SubmissionSetStatus=Original pointing from the SubmissionSet to each ExtrinsicObject
Optionally create a Folder RegistryPackage object and associate documents to it using Association objects of type HasMember, setting the targetObject to each document's entryUUID
Add the complete ObjectRefList and RegistryObjectList to the ProvideAndRegisterDocumentSet-b request body and validate the ebXML structure before transmission
Known gotchas
Each entryUUID must be locally unique within the submission and prefixed with urn:uuid: — reusing an entryUUID that already exists in the registry will cause a registration conflict error
The Association between a SubmissionSet and its documents requires the submissionSetStatus slot set to Original for new documents or Reference for documents already registered in another community's registry
Folders can only be created or updated in the same submission that references them — a document cannot be added to an existing folder via a new submission unless the folder is included as a RegistryPackage in the new SubmissionSet
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp