Binary resource?

[michelemottini]

How can we handle resources referencing binary data like report:

{
        "resourceType": "DiagnosticReport",
        "id": "7765466",
        . . . 
        "subject": {
          "reference": "Patient/4342009",
          "display": "SMART, NANCY"
        },
        "encounter": { "reference": "Encounter/4277906" },
        "effectiveDateTime": "2018-03-01T17:07:08.000Z",
        "issued": "2018-03-01T17:11:10.000Z",
        "performer": {
          "reference": "Practitioner/4474007",
          "display": "Pickering, Kathy"
        },
        "request": [ { "reference": "ProcedureRequest/23441893" } ],
        "presentedForm": [
          {
            "contentType": "text/html",
            "url": "https://fhir-myrecord.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Binary/TR-7765466"
          },
          {
            "contentType": "application/pdf",
            "url": "https://fhir-myrecord.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Binary/XR-7765466"
          }
        ]
      }

(Coming from Cerner)

Binary resource cannot be exported in ndjson files

[jmandel]

I see a few possible answers here:

1. No special treatment; a client can follow links if needed to retrieve binary content referenced from the exported resources (which is easy to specify, but leaves the problem out of scope, and thus unsolved)

2. Explicit export a set of Binary files, re-encoding each Binary resource with ndjson rows like this(which is standard FHIR, but which is inefficient)

3. Do something else clever. For example, defining some kind of more efficient "referenced content manifest file"