EHI Export API IG
0.1.0 - ci-build

EHI Export API IG, published by Argonaut. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/argonautproject/ehi-api/ and changes regularly. See the Directory of published versions

Resource Profile: EHIDocumentReference

Official URL: http://fhir.org/argonaut/ehi-api/StructureDefinition/ehi-document-reference Version: 0.1.0
Draft as of 2023-09-07 Computable Name: EHIDocumentReference

Profile for DocumentReference resources provided as metadata for non-FHIR content in an EHI export. Note that these resources would be minified and included as a single line in an NDJSON file

EHI Servers are encouraged to make use of DocumentReference properties and FHIR extensions in addition to those highlighted in this profile to incorporate any other relevant metadata about the files being referenced, such as their creation date or number of pages.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from DocumentReference

NameFlagsCard.TypeDescription & Constraintsdoco
.. DocumentReference 0..*DocumentReferenceA reference to a document
... meta 1..1MetaMetadata about the resource
.... Slices for tag 1..*CodingTags applied to this resource
Slice: Unordered, Open by pattern:$this
..... tag:ehi 1..1CodingEHI export tag
Required Pattern: At least the following
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: ehi-export
...... display1..1stringRepresentation defined by the system
Fixed Value: generated as part of an ehi-export request
... description 0..1stringShould be populated if possible. How to process the file (e.g., links to data dictionary or developer documentation).
... content
.... attachment
..... contentType 0..1codeShould be populated if possible. Mime type of the content.
..... size 0..1unsignedIntShould be populated if possible. Number of bytes of content.
.... format 0..1CodingShould be populated if possible. Vendor-specific for the provided data format, so clients can apply consistent processing.
..... system 1..1uriURL for the vendor's EHI Export documentation
..... code 1..1codeCode specific to the file's format
..... display 0..1stringHuman-readable descriptor for the file's format

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron