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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Composition is a resource in eHealth that bundle some resources together. Which resources should be bundled are mention in definite composition with the help of structure definition

Overview

  1. As for now every composition is associated with one of medical documents in Ukraine, while composition is not a document by itself.
  2. Composition use created with transaction resources in eHealth
  3. Composition is saved to DB in separate collection, and has its own composition.id
  4. Composition could not be changed
  5. Composition should not be signed by DS
  6. Each type of composition have it's own methods POST and GET

Common composition validations

  1. Validate access_token
  2. Validate scope 

Compositions in e-Health

Composition Structure

HL7NameTypeM/ODescriptionResult
"identifier" : { Identifier }, // Version-independent identifier for the Composition
iduuidM
ok
"status" : "<code>", // R! preliminary | final | amended | entered-in-errorstatusenum Mdic.:composition_statuses(final, entrered_in_error)ok
"type" : { CodeableConcept }, // R! Kind of composition (LOINC if possible)typeCodeableConcept
LOINC-??
"category" : [{ CodeableConcept }], // Categorization of Composition



?
"subject" : { Reference(Any) }, // Who and/or what the composition is aboutsubjectuuidMpatient_idok
"encounter" : { Reference(Encounter) }, // Context of the CompositionencounterReference(Encounter)M
ok
"date" : "<dateTime>", // R! Composition editing timedatedateTimeM

"author" : [{ Reference(Practitioner|PractitionerRole|Device|Patient|RelatedPerson|Organization) }], // R! Who and/or what authored the compositionauthorReference(employee)Mcould be taken from token

ok

"title" : "<string>", // R! Human Readable name/titletitlestring(2000)O
ok
"confidentiality" : "<code>", // As defined by affinity domain




"attester" : [{ // Attests to accuracy of composition
"mode" : "<code>", // R! personal | professional | legal | official
"time" : "<dateTime>", // When the composition was attested
"party" : { Reference(Patient|RelatedPerson|Practitioner|PractitionerRole|
Organization) } // Who attested the composition
}],
attesterReference(employee)M
ok
"custodian" : { Reference(Organization) }, // Organization which maintains the compositioncustodianReference(legal_entity)Mcould be taken from tokenok
"relatesTo" : [{ // Relationships to other compositions/documents
"code" : "<code>", // R! replaces | transforms | signs | appends
// target[x]: Target of the relationship. One of these 2:
"targetIdentifier" : { Identifier }
"targetReference" : { Reference(Composition) }
}],




?
"event" : [{ // The clinical service(s) being documented
"code" : [{ CodeableConcept }], // Code(s) that apply to the event being documented
"period" : { Period }, // The period covered by the documentation
"detail" : [{ Reference(Any) }] // The event(s) being documented
}],





"section" : [{ // Composition is broken into sections
"title" : "<string>", // Label for section (e.g. for ToC)
"code" : { CodeableConcept }, // Classification of section (recommended)
"author" : [{ Reference(Practitioner|PractitionerRole|Device|Patient|
RelatedPerson|Organization) }], // Who and/or what authored the section
"focus" : { Reference(Any) }, // Who/what the section is about, when it is not about the subject of composition
"text" : { Narrative }, // C? Text summary of the section, for human interpretation
"mode" : "<code>", // working | snapshot | changes
"orderedBy" : { CodeableConcept }, // Order of section entries
"entry" : [{ Reference(Any) }], // C? A reference to data that supports this section
"emptyReason" : { CodeableConcept }, // C? Why the section is empty
"section" : [{ Content as for Composition.section }] // C? Nested Section
}]







  • No labels