Project: Create web components for FHIR Resources

This is the thread for Project: Create web components for FHIR Resources

The coding session starts today. For ease of access to the updates about this project, here are the links to my weekly blog posts and feedbacks.

Weekly blog posts:

Weekly feedbacks: Google Summer of Code Weekly Feedback

Also, I have forked the GitLab project where I will be creating new components here. I will create Issues and merge requests to monitor my progress for approval by my mentor @sunbiz .

Based on the currently available components. We should start with 4 basic workflows which are; Creating a new patient record, finding a patient record, creating a new location, and creating a new organization. Pari and I have a meeting scheduled later today to iron out the workflow. Once that is done, we will create the issue and the Wiki for the project. Then she can start working continue working on the prototype.

@bolu, Sounds like a good plan. But please go back to my original discussion. If you agree, please create issues and sub-issues as tasks that will be done. Document the output of non-coding tasks on the wiki. Please feel free to disagree and discuss:

  1. Come up with 3-4 user personas (registration clerk, registration clerk at outpatient, general physician, nurse, etc. – prioritize for the most important ones) – document their roles, duties, experience, etc. This should be common practice for UX designers.

  2. The basic workflows that you listed are good. However, they are different for each user persona. E.g. new patient registration by the registration clerk, vs patient check-in (slide 7 from ONC’s template). Those should be treated differently, and might be customizations on the same web component. Prioritize which workflows for which personas.

  3. Look at that ONC workflow template for different forms or data entry points in a workflow. That will give you some probable fields that can be part of one or multiple forms. This should help create wireframes for the prioritized workflows for the prioritized personas.

  4. Map the fields in the wireframe to FHIR resources and test out the FHIR calls to a test HAPI server.

  5. Create high-fidelity designs in Adobe XD that can be exported to HTML/CSS.

  6. Break out into the smallest unit web component that can exist on its own with the FHIR resource. Write a polymer component/class for it.

1 Like

@sunbiz I have a clearer picture of what is required now. I will start on these and I will have the accompanying documentation in the wiki and issues

Yes, working on the personas.

@sunbiz I have created two issues, one for creating personas and the other for creating a workflow for each persona

1 Like

GitLab wiki page created for four Personas

@sunbiz I added a new package to my forked librehealth-webcomponents repo and I ran the lerna bootstrap --use-workspaces but I can get the custom element to work. what do you think might be the cause? I checked for the version of polymer, the one indicated in the workspace’s package.json was 0.5.2 but i have the version 0.7.1. installed locally.

@bolu get into the habit of sharing your posts when you make them. This is part of how I double check:

Oh okay, I will. I posted my last blog yesterday

1 Like

All good – we do have LibreHealth Planet but i’m not sure how many people use it

I just checked it out. It makes it easy to check up on all the projects. Pretty cool

Link to the week 7 Blog Post

@bolu Commenting so that you can post. :slight_smile:

1 Like
1 Like

I have worked on creating EHR screens. The first upload shows find patient and register patient details.

1 Like

Worked on the Visit tab for patient medication ( need to do some modifications more) Attaching the previous idea before feedback

1 Like

@parishmita.bora. I think its come together pretty well. The workflows look seamless but could be improved on. As I mentioned previously, we could enlarge the new RX window to make it more convenient to make prescriptions. Also providing a brief overview of the medication and Allergy history as you have in the video is nice.

This week, I decided to bring together most of the observation resources I have created so far. Because there are various categories of observations ranging from vital signs to labs and different use of observation resource from a physician making an observation in an observation note, to a record of vital signs and to the ordering and reporting of labs. I think the components would have a wide range of use. Below is a snippet of some of the components.

While a majority of the components have input fields in form of textboxes and drop down menu, I felt that the reference range component should use a span tag. This is because, it would be rather unusual to have a physician/radiologist/lab technician inputting the reference range of an observation. It seems like its general practice that those values are displayed based on the age and population the patient belongs. @sunbiz and @judywawira, please provide a feedback your perception of my progress. Thanks

1 Like