A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference.

Identifiers associated with the image - these may include identifiers for the image itself, identifiers for the context of its collection (e.g. series ids) and context ids such as accession numbers or other workflow identifiers.

The identifier label and use can be used to determine what kind of identifier it is.

A procedure that is fulfilled in whole or in part by the creation of this media.

Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.

A larger event of which this particular event is a component or step.

E.g. Drug administration as part of a procedure, procedure as part of observation, etc.

Not to be used to link an event to an Encounter - use Event.context for that.

[The allowed reference resources may be adjusted as appropriate for the event resource].

The current state of the {{title}}.

A nominal state-transition diagram can be found in the [[event.html#statemachine | Event pattern]] documentation

Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.

A code that classifies whether the media is an image, video or audio recording or some other media category.

Used for filtering what observations are retrieved and displayed.

Details of the type of the media - usually, how it was acquired (what type of device). If images sourced from a DICOM system, are wrapped in a Media resource, then this is the modality.

The name of the imaging view e.g. Lateral or Antero-posterior (AP).

Who/What this Media is a record of.

The encounter or episode of care that establishes the context for this media.

Links the media to the Encounter context.

This will typically be the encounter the media occurred within.

The date and time(s) at which the media was collected.

The date and time this version of the media was made available to providers, typically after having been reviewed.

It may be the same as the lastUpdated time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the lastUpdated time of the resource itself due to a non-clinically significant update that does not require the new version to be reviewed and verified again.

The person who administered the collection of the image.

Describes why the event occurred in coded or textual form.

Textual reasons can be captured using reasonCode.text.

Indicates the site on the subject's body where the observation was made (i.e. the target site).

Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component.

If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension body-structure.

The name of the device / manufacturer of the device that was used to make the recording.

The device used to collect the media.

An extension should be used if further typing of the device is needed. Secondary devices used to support collecting a media can be represented using either extension or through the Observation.related element.

Height of the image in pixels (photo/video).

Width of the image in pixels (photo/video).

The number of frames in a photo. This is used with a multi-page fax, or an imaging acquisition context that takes multiple slices in a single image, or an animated gif. If there is more than one frame, this SHALL have a value in order to alert interface software that a multi-frame capable rendering widget is required.

The duration of the recording in seconds - for audio and video.

The duration might differ from occurrencePeriod if recording was paused.

The actual content of the media - inline or by direct reference to the media source file.

Recommended content types: image/jpeg, image/png, image/tiff, video/mpeg, audio/mp4, application/dicom. Application/dicom can contain the transfer syntax as a parameter. For media that covers a period of time (video/sound), the content.creationTime is the end time. Creation time is used for tracking, organizing versions and searching.

Comments made about the media by the performer, subject or other participants.

Not to be used for observations, conclusions, etc. Instead use an Observation based on the Media/ImagingStudy resource.