Skip to main content

Eka FHIR Resource Mappings

This document provides the FHIR (Fast Healthcare Interoperability Resources) mappings used by Eka Care for structured medical data. Each section details how Eka properties map to standard FHIR resources.

Symptoms

FHIR Resource: Observation Symptoms observed during patient consultations are stored using the FHIR Observation resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
symptoms.name, codeObservation.codeManifestation or SymptomSNOMED, Eka codes
symptoms.categoryObservation.categoryObservation CategorySNOMED: 418799008, MDB: s-8068301606
symptoms.statusObservation.statusObservation StatusVoice2RX: preliminary, Rx: final
symptoms.sinceObservation.effective-effectiveDateTime | effectivePeriod
symptom.notesObservation.noteAnnotationString text
symptom.is-recorded-forObservation.subject-Patient Reference
symptoms.severityObservation.valueCodeableConceptValueCodeableConcept
symptoms.lateralityObservation.bodySiteBody SiteCodeableConcept.coding.code

Conditions / Diagnoses

FHIR Resource: Condition Medical conditions and diagnoses are stored using the FHIR Condition resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
condition.name, codeCondition.code-SNOMED
condition.current_statusCondition.clinicalStatusCondition ClinicalRuled-out: inactive, Confirmed: active, Suspected: unknown
condition.verificationCondition.verificationStatusVerification StatusRuled-out: refuted, Confirmed: confirmed, Suspected: unconfirmed
condition.severityCondition.severityCondition SeveritySNOMED: 24484000 (severe), 6736007 (moderate), 255604002 (mild)
condition.categoryCondition.categoryCondition CategoryFHIR: encounter-diagnosis
condition.sinceCondition.onset-datetime | period | age | string
condition.is-recorded-forCondition.subject-Patient
condition.first-time-onCondition.recordedDate--
condition.evidenceCondition.evidence-Evidence pointing to condition
condition.whereCondition.bodyStructure-Has bodysite + other details
condition.stageCondition.stage-e.g., cancer stages
condition.notesCondition.note-Strings
condition.lateralityCondition.bodySiteBody SiteCodeableConcept.coding.code

Medical History

FHIR Resource: Condition Past medical history is also stored using the FHIR Condition resource with different category.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
condition.name, codeCondition.code-SNOMED
condition.current_statusCondition.clinicalStatusCondition ClinicalRuled-out: inactive, Confirmed: active, Suspected: unknown
condition.verificationCondition.verificationStatusVerification StatusRuled-out: refuted, Confirmed: confirmed, Suspected: unconfirmed
condition.severityCondition.severityCondition SeveritySNOMED codes for severity
condition.categoryCondition.categoryCondition Categoryproblem-list-item
condition.sinceCondition.onset-datetime | period | age | string
condition.is-recorded-forCondition.subject-Patient
condition.first-time-onCondition.recordedDate--
condition.stageCondition.stage-e.g., cancer stages
condition.notesCondition.note-Strings

Advices

FHIR Resource: CarePlan Doctor’s advice to patients is stored using the FHIR CarePlan resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
advice.statusCarePlan.status-active
advice.intentCarePlan.intentCare Plan Intentplan
advice.categoryCarePlan.category-Custom: SNOMED for advice
advice.forCarePlan.subject-Patient
advice.detailsCarePlan.activity.performedActivityCodeableReferenceCodeableReference.concept.text
advice.detailsCarePlan.descriptionCarePlan Description-

Notes

FHIR Resource: CarePlan Clinical notes are stored using the FHIR CarePlan resource with different intent.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
notes.statusCarePlan.status-active
notes.intentCarePlan.intentCare Plan Intentproposal
notes.categoryCarePlan.category-Custom: for notes
notes.forCarePlan.subject-Patient
notes.detailsCarePlan.descriptionCodeableReferenceCodeableReference.concept.text

Examinations

FHIR Resource: Observation Physical examination findings are stored using the FHIR Observation resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
exam.name, codeObservation.codeManifestation or SymptomSNOMED, Eka codes
exam.categoryObservation.categoryObservation Categoryexam
exam.statusObservation.statusObservation Statuspreliminary | final | unknown
exam.sinceObservation.effective-effectiveDateTime | effectivePeriod
exam.notesObservation.noteAnnotationString
exam.is-recorded-forObservation.subject-Patient
exam.locationObservation.bodySiteBody Site-

Follow-Up

FHIR Resource: Appointment Follow-up appointments suggested by doctors are stored using the FHIR Appointment resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
followup.statusAppointment.statusAppointment Statusproposed
followup.typeAppointment.appointmentTypeAppointment TypeFOLLOWUP
followup.createdAppointment.created--
followup.startAppointment.start-Instant

Family History

FHIR Resource: FamilyMemberHistory Family medical history is stored using the FHIR FamilyMemberHistory resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
dataentry.statusFamilyMemberHistory.statusHistory Statuscompleted
relationFamilyMemberHistory.relationshipFamily Member-
relative.nameFamilyMemberHistory.name-String
remarksFamilyMemberHistory.note--
clinical.statusFamilyMemberHistory.condition.outcome-CodeableConcept.coding.code

Vitals ( Trackers )

FHIR Resource: Observation Patient vitals and health trackers are stored using the FHIR Observation resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
vitals.name, codeObservation.codeManifestation or SymptomSNOMED, Eka codes
vitals.categoryObservation.categoryObservation CategorySNOMED: s-8068301606, FHIR: vital-signs
vitals.statusObservation.statusObservation StatusVoice2RX: preliminary, Rx: final
vitals.sinceObservation.effective-effectiveDateTime | effectivePeriod
vitals.notesObservation.noteAnnotationString text
vitals.valueObservation.valueCodeableConceptValueCodeableConcept
vitals.componentsObservation.component-For vitals like BP with multiple values

Medications

FHIR Resource: MedicationRequest Medication prescriptions are stored using the FHIR MedicationRequest resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
medication.name, medication.idMedicationRequest.medicationCodeableConceptMedication CodesName : Ibuprofen 200mg; code: MDB/SNOMED
medication.statusMedicationRequest.statusMedicationRequest Statusactive
medication.intentMedicationRequest.intentMedicationRequest Intentorder
patient.id, patient.profile.personal.nameMedicationRequest.subjectReferencePatient reference
doctor.id, doctor.profile.personal.nameMedicationRequest.requesterReferencePractitioner reference
dateMedicationRequest.authoredOndateTimeISO 8601 format
medication.instructionMedicationRequest.dosageInstruction.textDosageString
medication.dose.value, dose.unit, dose.id, dose.customMedicationRequest.dosageInstruction.doseAndRate.doseQuantityQuantityvalue, unit, code
medication.dose-rate-typeMedicationRequest.dosageInstruction.doseAndRate.typeDose Rate Typeordered
medication.frequency.id, frequency.value, frequency.customMedicationRequest.dosageInstruction.additionalInstructionAdditional InstructionCodeableConcept
medication.frequency.frequency, frequency.period, frequency.period_unit, duration, duration-unit, whenMedicationRequest.dosageInstruction.timing.repeatTimingfrequency, period, periodUnit
calculatedMedicationRequest.dispenseRequest.quantityQuantityfrequency × duration × dose

Lab Tests / Imaging / Surgical Procedures

FHIR Resource: ServiceRequest Lab tests, imaging requests ( radiology) and surgical procedure are stored using the FHIR ServiceRequest resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
statusServiceRequest.statusRequest Statusactive
intentServiceRequest.intentRequest Intentorder
categoryServiceRequest.categoryService Request CategorySupported categories are imaging, lab_test, surgical_procedure
labTests.id, labTests.nameServiceRequest.codeProcedure CodesCodeableConcept from http://eka.care/mdb, http://loinc.org, https://parchi.eka.care/local
patient_oid, patient_nameServiceRequest.subjectReferenceReference to Patient resource
visitidServiceRequest.encounterReferenceReference to Encounter resource
doctor_oid, doctor_nameServiceRequest.requesterReferenceReference to Practitioner resource
dateServiceRequest.authoredOndateTimeISO 8601 format
remark/notesServiceRequest.noteAnnotationText note

DrugAllergy / FoodAllergy Intolerance

FHIR Resource: AllergyIntolerance Food and medication allergies are stored using the FHIR AllergyIntolerance resource.
Eka PropertyFHIR ResourceFHIR LinkDecision to Use
doctor_oid, doctor_nameAllergyIntolerance.asserterReferenceReference to Practitioner resource
categoryAllergyIntolerance.categoryAllergy Categoryfood or medication
clinicalStatusAllergyIntolerance.clinicalStatusClinical Statuscode: active, display: Active
drugAllergy.id, foodOtherAllergy.idAllergyIntolerance.codeAllergy CodesCodeableConcept from http://snomed.info/sct, http://eka.care/mdb, https://parchi.eka.care/local
criticalityAllergyIntolerance.criticalityAllergy Criticalityhigh
notesAllergyIntolerance.noteAnnotationText note
patient_oid, patient_nameAllergyIntolerance.patientReferenceReference to Patient resource
typeAllergyIntolerance.typeAllergy Typeallergy
recordedDateAllergyIntolerance.recordedDatedateTimeISO 8601 format (current time)
verificationStatusAllergyIntolerance.verificationStatusVerification Statuscode: confirmed, display: Confirmed

Summary Table

Data TypeFHIR ResourceCategory/Type
SymptomsObservationsigns-and-symptoms
Conditions/DiagnosesConditionencounter-diagnosis
Medical HistoryConditionproblem-list-item
AdvicesCarePlanintent: plan
NotesCarePlanintent: proposal
ExaminationsObservationexam
Follow-UpAppointmentFOLLOWUP
Family HistoryFamilyMemberHistory-
VitalsObservationvital-signs
MedicationsMedicationRequestintent: order
Lab Tests/Imaging/Surgical ProceduresServiceRequestimaging/lab_test/surgical_procedure
Food and drug AllergiesAllergyIntolerancefood/medication