Issue : The open source version of growth chart gets the Father/Mother heights from the FamilyHistory resource. If an EHR has not implemented the Family History FHIR resource then the application provides for no other way to automatically get these heights from the patients chart thus leaving the user with an option to manually enter the heights using the Settings gear icon.
Solution : If the EHR has availability for Observation's resource then it can leverage 2 Parental Height LOINC's(83845-8 , 83846-6) to fetch the necessary heights. This change adds the ability to use LOINC's using the Observation's resource to fetch Father/Mother heights from the EHR.
Consideration: In this change the app attempts to make the FamilyHistory resource call but also request observation's for these additional LOINC's (for parental heights) and uses the heights returned by the LOINC's if FamilyHistory resource call fails.
Issue : The open source version of growth chart gets the Father/Mother heights from the FamilyHistory resource. If an EHR has not implemented the Family History FHIR resource then the application provides for no other way to automatically get these heights from the patients chart thus leaving the user with an option to manually enter the heights using the Settings gear icon.
Solution : If the EHR has availability for Observation's resource then it can leverage 2 Parental Height LOINC's(83845-8 , 83846-6) to fetch the necessary heights. This change adds the ability to use LOINC's using the Observation's resource to fetch Father/Mother heights from the EHR.
Consideration: In this change the app attempts to make the FamilyHistory resource call but also request observation's for these additional LOINC's (for parental heights) and uses the heights returned by the LOINC's if FamilyHistory resource call fails.