Variable DocumentReferenceContentSchemaConst

Content element for DocumentReference - links to the actual binary content.

Relationship Between Resources

The architecture adds DocumentReference as a metadata layer without modifying Binary:

DocumentReference                    BinaryFileSchema (unchanged)
├── type (LOINC)                     ├── file_type (MIME/contentType)
├── subject                          ├── controller_did
└── content[].attachment.url ────────┤
    = "binary/{_id}"                 ├── url (welshare://) ← internal storage URL
                                     └── reference (existing, for questionnaire attachments)
Copy

Reference Flow

1. DocumentReference → Binary: Use makeBinaryReference to create references:

   • makeBinaryReference(binaryId).reference → "binary/{id}"
   • This reference is stored in content[].attachment.url

2. Binary → S3: Binary resource's url field points to actual content:

   • url = "welshare://{key}" (internal, for content retrieval)

3. Binary.reference (deprecated, backwards compatibility): Used for questionnaire field references