Patient Record
Patient demographics and other administrative information about a patient is store as Patient (MY Core) record.
Click MY Core postman API link to view common API used in HIE.
[base] = address url e.g. "https://fhir.hie.moh.gov.my/baseR4/" [type] = resource type e.g. "Patient | Encounter | Composition" @patientId = unique patient id defined from source system e.g "patient-sample" @patientIdentifier = patient identifier such as mykad number or MRN e.g "HIE-00000003"
| Sample Description | Sample Body | API Method | API |
|---|---|---|---|
| Create/Update patient record | PUT | [base]/Patient/@patientId | |
| Retrieve patient record with id | - | GET | [base]/Patient/@patientId |
| Retrieve patient record with identifier | - | GET | [base]/Patient?identifier=@patientIdentifier |
Identifier Type
Patient (MY Core) support certain type of identifier, however each record must at least have a facility mrn Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/patient-mrn').value.
- MyKad or MyKid is store as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/my-kad-no').value. - Army identifier is store as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/army-no').value. - Police identifier is stored as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/police-no').value. - Newborn identifier format according to SMRP standard is
[MotherIdentifier] E/[Child No]. Example "921105146670 E/1".- It is stored as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/newborn-no').value. - However, it is not mandatory for a source system to send in this format.
- It is stored as
- Other type of identifier is store as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/others-no').value.- This includes unknown patient where HIE format is
[facility mnemonic]-UNK-[last 2 year digit][6 digit running number]. Example, "HTJ-UKN-23000006". - However, it is not mandatory for a source system to send in this format.
- This includes unknown patient where HIE format is
Golden Record
Due to the scope of integration, a single individual is expected to have multiple patient record from various source system in HIE. These records are linked together under one golden record using a function known as Master Data Management (MDM) developed by smileCDR.
Diagram below showing an example of records from various source system linked by a golden record in HIE.
The server will link multiple patient record to a single golden record based on these 4 element values:
- Name
Patient.name.give, - Birth Date
Patient.birthDate, - Any Identifier
Patient.identifier.value, - Gender
Patient.gender.
For each patient record created in the HIE server, the server will check if a golden record with above details match with any golden record existed in the server, if match it will link the golden record. If no match exist, a new golden record will be created linked to the created patient record.
Merge and Unmerge Record
This section briefly explains the concept of merge and unmerge support functionality in HIE. However, it is done mainly through case by case basis using Rekod Pesakit (Provider Portal) interface only. Generally there are 2 scenario:
If multiple patient records are found to be duplicates, they can be linked together, as described below.
- If user detect that a duplicate record exist related to a same patient they can perform a merge record. A qualified user can select the main record (the one with most complete or correct information) as the main golden record and merge with the duplicate reccord. The record merged will link with the new golden record and inactive the duplicate golden record.
If a patient records are found to be wrongly merged, they can be seperated as described below.
- If user detect that a record was mistakenly merge that is supposed to be 2 different patient. A qualified user can select the wrongly merge record and detach itself from the original golden record, this will create a new golden record from the detached record.
Identifier Type
Patient (MY Core) support certain type of identifier, however each record must at least have a facility mrn Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/patient-mrn').value.
- MyKad or MyKid is store as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/my-kad-no').value. - Army identifier is store as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/army-no').value. - Police identifier is stored as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/police-no').value. - Newborn identifier format according to SMRP standard is
[MotherIdentifier] E/[Child No]. Example "921105146670 E/1".- It is stored as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/newborn-no').value. - However, it is not mandatory for a source system to send in this format.
- It is stored as
- Other type of identifier is store as
Patient.identifier.where (system ='http://fhir.hie.moh.gov.my/sid/others-no').value.- This includes unknown patient where HIE format is
[facility mnemonic]-UNK-[last 2 year digit][6 digit running number]. Example, "HTJ-UKN-23000006". - However, it is not mandatory for a source system to send in this format.
- This includes unknown patient where HIE format is
Golden Record
Due to the scope of integration, a single individual is expected to have multiple patient record from various source system in HIE. These records are linked together under one golden record using a function known as Master Data Management (MDM) developed by smileCDR.
Diagram below showing an example of records from various source system linked by a golden record in HIE.
The server will link multiple patient record to a single golden record based on these 4 element values:
- Name
Patient.name.give, - Birth Date
Patient.birthDate, - Any Identifier
Patient.identifier.value, - Gender
Patient.gender.
For each patient record created in the HIE server, the server will check if a golden record with above details match with any golden record existed in the server, if match it will link the golden record. If no match exist, a new golden record will be created linked to the created patient record.
Merge and Unmerge Record
This section briefly explains the concept of merge and unmerge support functionality in HIE. However, it is done mainly through case by case basis using Rekod Pesakit (Provider Portal) interface only. Generally there are 2 scenario:
If multiple patient records are found to be duplicates, they can be linked together, as described below.
- If user detect that a duplicate record exist related to a same patient they can perform a merge record. A qualified user can select the main record (the one with most complete or correct information) as the main golden record and merge with the duplicate reccord. The record merged will link with the new golden record and inactive the duplicate golden record.
If a patient records are found to be wrongly merged, they can be seperated as described below.
- If user detect that a record was mistakenly merge that is supposed to be 2 different patient. A qualified user can select the wrongly merge record and detach itself from the original golden record, this will create a new golden record from the detached record.