Entity & other comparison

1. Difference kinds of organization

HL7

"Organisation"."type" : [{ CodeableConcept }] https://www.hl7.org/fhir/codesystem-organization-type.html

Code	Display	Definition
prov	Healthcare Provider	An organization that provides healthcare services.
dept	Hospital Department	A department or ward within a hospital (Generally is not applicable to top level organizations)
team	Organizational team	An organizational team is usually a grouping of practitioners that perform a specific function within an organization (which could be a top level organization, or a department).
govt	Government	A political body, often used when including organization records for government bodies such as a Federal Government, State or Local Government.
ins	Insurance Company	A company that provides insurance to its subscribers that may include healthcare related policies.
edu	Educational Institute	An educational institution that provides education or research facilities.
reli	Religious Institution	An organization that is identified as a part of a religious institution.
crs	Clinical Research Sponsor	An organization that is identified as a Pharmaceutical/Clinical Research Sponsor.
cg	Community Group	An un-incorporated community group.
bus	Non-Healthcare Business or Corporation	An organization that is a registered business or corporation but not identified by other types.
other	Other	Other type of organization not already specified.

e-Health

[legal_entities].type | DICTIONARY: LEGAL_ENTITY_TYPE

"values": {
"MSP": "заклад з надання медичних послуг",
"MIS": "Medical Information system"
},
"name": "LEGAL_ENTITY_TYPE"

Problem/Difference

In HL7 type its array (many kinds), in the e-Health Legal Entity - one value of type
In HL7 type "prov" (Healthcare Provider) its crossing of 2 or more types of e-Health

2. Hierarchical structure of organization

HL7

Supports hierarchy by attribute "Part of"

e-Health

Non supports hierarchy of Legal Entity

Problem/Difference

Missing functionality

3. Medical services structure of organization/locations

HL7

Supports multi medical services (category + type) in location (division) at entity "healthcareservice" https://www.hl7.org/fhir/healthcareservice.html

e-Health

Now non support. May be use "Product Catalog" ???

Problem/Difference

Missing functionality

4. Confusion in practitioner quailifications/specializtion/etc

HL7

"Practitioner"."qualification"."code" : { CodeableConcept } - https://www.hl7.org/fhir/v2/0360/2.7/index.html#definition

e-Health

Other structure of quailification

### Qualification
+ type: SPECIALIZATION (string, required) - `Dictionary QUALIFICATION_TYPE`
+ institution_name: Академія Богомольця (string, required)
+ speciality: Педіатр (string, required)
+ issued_date: 2017-02-28 (string, required) - дата отримання сертифікату
+ certificate_number: 2017-02-28 (string, required)

Problem/Difference

Big confusion and incompatibility of practitioner quailifications/specialization/etc

May be its non confusion, but it simply kind of education/quailifications specific in UA.

5. Absent practitioner role

HL7

"PractitionerRole" -A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. https://www.hl7.org/fhir/practitionerrole.html#resource

e-Health

Non supports sets Roles/Divisions/specialties/services for Employee.

Problem/Difference

Missing functionality

Data structure comparison

Organization

https://www.hl7.org/fhir/organization.html

HL7	e-Health	Result
Organization	[legal_entities]
"identifier" : [{ Identifier }]	id \| uuid \| not null	Ok
"active" : <boolean>	status \| enum('active','closed') \| not null	Ok
"type" : [{ CodeableConcept }]	type \| varchar \| not null	Ok
"name" : "<string>"	name \| varchar \| not null	Ok
"alias" : ["<string>"], // A list of alternate names that the organization is known as, or was known as in the past	???	Small problem
"telecom" : [{ ContactPoint }]	phones \| jsonb[]	Ok
"telecom" : [{ ContactPoint }]	email \| varchar	Ok
"partOf" : { Reference(Organization) },	???	Problem
"contact" : [{ // Contact for the organization for a certain purpose}]	[employees]	Ok
→"purpose" : { CodeableConcept }, // The type of contact	[employees].employee_type	Ok
→"name" : { HumanName }, // A name associated with the contact	[employees].[parties].first_name + last_name	Ok
→"telecom" : [{ ContactPoint }], // Contact details (telephone, email, etc.) for a contact	[employees].[parties].phones	Ok
→"address" : { Address } // Visiting or postal addresses for the contact	[employees].[parties].???	Small problem
"endpoint" : [{ Reference(Endpoint) }]	redirect_uri ???	Small problem

Location

https://www.hl7.org/fhir/location.html

HL7	e-Health	Result
Location	[divisions]
"identifier" : [{ Identifier }]	id \| uuid \| not null	Ok
"status" : "<code>", // active \| suspended \| inactive	status \| varchar \| not null	Ok
"operationalStatus" : { Coding }, // The Operational status of the location (typically only for a bed/room)	???	Small problem
"name" : "<string>", // Name of the location as used by humans	name \| varchar \| not null	Ok
"alias" : ["<string>"], // A list of alternate names that the location is known as, or was known as in the past	???	Small problem
"description" : "<string>", // Additional details about the location that could be displayed as further information to identify the location beyond its name	???	Small problem
"mode" : "<code>", // instance \| kind	???	Small problem
"type" : { CodeableConcept }, // Type of function performed	type \| varchar \| not null	Ok
"telecom" : [{ ContactPoint }], // Contact details of the location	phones \| jsonb[] \| not null email \| varchar	Ok
"address" : { Address }, // Physical location	addresses \| jsonb \| not null	Ok
"physicalType" : { CodeableConcept }, // Physical form of the location	???	Ok
"position" : { // The absolute geographic location	location \| geometry	Ok
→"longitude" : <decimal>, // R! Longitude with WGS84 datum	location \| geometry	Ok
→"latitude" : <decimal>, // R! Latitude with WGS84 datum	location \| geometry	Ok
→"altitude" : <decimal> // Altitude with WGS84 datum	location \| geometry	Ok
"managingOrganization" : { Reference(Organization) }, // Organization responsible for provisioning and upkeep	legal_entity_id \| uuid \| not null	Ok
"partOf" : { Reference(Location) }, // Another Location this one is physically part of	???	Small problem
"endpoint" : [{ Reference(Endpoint) }] // Technical endpoints providing access to services operated for the location	redirect_uri ???	Small problem

Practitioner

https://www.hl7.org/fhir/practitioner.html

HL7	e-Health	Result
Practitioner	[employees]
"identifier" : [{ Identifier }]	id \| uuid \| not null	Ok
"active" : <boolean>, // Whether this practitioner's record is in active use	is_active \| boolean \| not null	Ok
"name" : [{ HumanName }], // The name(s) associated with the practitioner	[parties].first_name + last_name	Ok
"telecom" : [{ ContactPoint }], // A contact detail for the practitioner (that apply to all roles)	[parties].phones	Ok
"gender" : "<code>", // male \| female \| other \| unknown	[parties].gender	Ok
"birthDate" : "<date>", // The date on which the practitioner was born	[parties].birth_date	Ok
"photo" : [{ Attachment }], // Image of the person	???	Small problem
"qualification" : [{ // Qualifications obtained by training and certification}]	[doctors].qualification	Ok
→"identifier" : [{ Identifier }], // An identifier for this qualification for the practitioner
→"code" : { CodeableConcept }, // R! Coded representation of the qualification	??? [doctors].[qualification]. type	Problem
→"period" : { Period }, // Period during which the qualification is valid	???	Small problem
→"issuer" : { Reference(Organization) } // Organization that regulates and issues the qualification	[doctors].[qualification].institution_name	Ok
"communication" : [{ CodeableConcept }] // A language the practitioner is able to use in patient communication	???	Small problem

HL7 comparison

Entity & other comparison

1. Difference kinds of organization

HL7

e-Health

Problem/Difference

2. Hierarchical structure of organization

HL7

e-Health

Problem/Difference

3. Medical services structure of organization/locations

HL7

e-Health

Problem/Difference

4. Confusion in practitioner quailifications/specializtion/etc

HL7

e-Health

Problem/Difference

5. Absent practitioner role

HL7

e-Health

Problem/Difference

Data structure comparison

Organization

Location

Practitioner