ЕСОЗ - публічна документація

RC_(MC-1164)_[NEW] ME/Composition data model

FHIR description

Composition - FHIR v5.0.0

Schema

 

Screenshot 2024-08-13 at 13.37.29.png

eHealth description

Composition

Collection name: compositions

Collection is used to store composition document

Composition document

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

id

string

M

System identifier of Composition (ObjectID)

Doesn't comply with FHIR

status

string

M

Composition status

Ok

type

{Codeable_concept}

M

Type of composition

Ok

category

{Codeable_concept}

M

Category of composition

Ok

According to FHIR - category is array

date

date_time

M

When the composition was signed

Ok

title

string

M

Human Readable name/title

Ok

subject

string

M

Hashed patient_id

Doesn't comply with FHIR (datatype)

custodian

{Reference}

M

Organization which maintains the composition

Ok

encounter

{Reference}

M

Context of the Composition

Ok

author

{Reference}

M

Who and/or what authored the composition

Ok

section

[Section]

O

Composition is broken into sections

Ok

extension

[Extension]

O

Extensions added to composition

Ok

relates_to

[Related_artifact]

O

Relationships to other compositions/documents

Ok

attester

[Attester]

M

Attests to accuracy of composition

Ok

event

[Event]

M

The clinical service(s) being documented

Ok

context_episode_id

string

M

Reference to episode of care

Doesn't comply with FHIR

signed_content_links

[string]

M

Reference on signed content in media storage

Doesn't comply with FHIR

authorize_withinform_with

string

O

Hashed patient authentication method used while creating composition

Doesn't comply with FHIR

status_reason

string

O

Reason for status of the Composition (used in mark-in-error process)

Doesn't comply with FHIR

explanatory_letter

string

O

Description for status of the Composition (used in mark_in_error process)

Doesn't comply with FHIR

Complex Types

Section

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

title

string

M

Label for section

Ok

code

{Codeable_concept}

M

Classification of section

Ok

author

[Reference]

M

Who and/or what authored the section

Ok

text

{Narrative}

O

Text summary of the section, for human interpretation

Ok

ordered_by

{Codeable_concept}

O

Order of section entries

Ok

entry

[Reference]

O

A reference to data that supports this section

Ok

empty_reason

{Codeable_concept}

O

Why the section is empty

Ok

section

[Section]

O

Nested Section if needed

Ok

Extension

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

code

string

M

Extension code

Doesn't comply with FHIR

value_[x]

 

M

One of <specific type> must be provided

Ok

  • value_codeable_concept

{CodeableConceptExtension}

 

 

 

  • value_decimal

number

 

 

 

Attester

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

mode

{Codeable_concept}

M

Composition attestation mode

Dictionary: COMPOSITION_ATTESTER_MODES

Ok

party

{Reference}

M

Who attested the composition

Ok

Event

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

code

{Codeable_concept}

M

Code that apply to the event being documented

Dictionary: COMPOSITION_EVENTS

Ok

According to FHIR - code is array

period

{Period}

M

The period covered by the documentation

Ok

CodeableConceptExtension

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

coding

[Coding]

M

 

Ok

text

string

O

Plain text representation of the concept

Ok

extension

[Extension]

O

 

Ok

Requisition number

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

Name

Type

M/O

Description and constraints

HL7 vs eHealth comparison result

id

UUID

M

System identifier of requisition number

Doesn't comply with FHIR

type

string

M

Entity type, example: “DRIVER”

Doesn't comply with FHIR

number

string

M

Hashed requisition(title)

Doesn't comply with FHIR

inserted_at

date_time

M

 

Doesn't comply with FHIR

inserted_by

date_time

M

 

Doesn't comply with FHIR

patient_id

string

M

Hashed patient id

Doesn't comply with FHIR

expiration_date

date_time

M

Date when record will be deleted

Doesn't comply with FHIR

entity

string

M

Resource type, example: “composition”

Doesn't comply with FHIR

ЕСОЗ - публічна документація