0.1.1-current - ci-build
0.1.1-current - ci-build
JohnMoehrkeTestBinary, published by John Moehrke (himself). This guide is not an authorized publication; it is the continuous build for version 0.1.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/JohnMoehrke/testBinary/ and changes regularly. See the Directory of published versions
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Just a simple profile of DocumentReference |
not much to say |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| A bundle with various Binary and DocumentReference examples |
A bundle containing various Binary and DocumentReference examples. |
| Binary example using Binary of json |
Example of a json hello world using Binary. |
| Binary example using Binary of pdf |
Example of a pdf hello world using Binary. |
| Binary example using Binary of png |
Example of a binary ink signature using Binary. |
| Binary example using Binary of text |
Example of a binary hello world using Binary. |
| Binary example using Binary of xml |
Example of a xml hello world using Binary. |
| DocumentReference text file data |
Example of a hello world binary using DocumentReference. This does not have the contentType specified, and it will be filled by ig-loader based on the file extension. |
| DocumentReference with many contents |
Example DocumentReference with many content of each kind of binary. |
| DocumentReferenceFoo example using Ink binary |
Example of a DocumentReference data of an ink signature png. |
| Failed DocumentReference text file because of populated contentType |
Example of a hello world binary using DocumentReference that fails because contentType is populated. This will result in a DocumentReference that has not been loaded with the attachment, but rather holding in the id field exactly what is in this example. |