USCDI
USCDI defines data classes and elements for interoperable health information exchange. These elements can be reused within MedLog records.FHIR
Fast Healthcare Interoperability Resources (FHIR) data formats and elements can also anchor MedLog entries to standardized clinical entities.Header
Header
AuditEvent.occurredPeriod can represent the execution
interval and
AuditEvent.recorded can
record when the MedLog record was logged.User identity
User identity
AuditEvent.agent can
identify the immediate calling service, with the account identifier recorded in
AuditEvent.agent.who.identifier
and security role in
AuditEvent.agent.role.
When possible, references to Practitioner or
PractitionerRole can link the account to the human
user and clinical role context.Target identity
Target identity
Target identity can reference an existing
Patient,
Appointment, or other appropriate resource, with
Encounter providing encounter context where applicable.Model instance
Model instance
A software model can be represented by a
Device containing
its identifier and software version.Inputs and outputs
Inputs and outputs
Inputs can reference
Observation or
DocumentReference, for example, while outputs can
use FHIR resources appropriate to their clinical meaning, such as
RiskAssessment for a risk prediction or
DocumentReference for a generated document.User feedback
User feedback
User feedback collected through a defined questionnaire can use
QuestionnaireResponse.These are only illustrative examples of the many possible FHIR fields which could be used to represent
or reference information in MedLog records. The
field mapping explorer shows the full set side by side with USCDI
and OpenTelemetry.