ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Designing Online Health Web Portal system

Updated on July 23, 2016

Introduction

The website must fulfill the usability goals and by extension the user experience goals. The ideal system ought to offer all services to virtually all types of customers and meet the usability goals and user experience expectations. However, this is not and most likely is never the case since. This is because of the challenges in developing systems. In this online web portal, there a few challenges that may affect the usability of the system that is based on the user physical, characteristic and technical capabilities.

Health web portal

Source

Challenges present in designing for patients with varying needs and technical ability

First of all under physical skills, some users have excellent eyesight, and yet there are others who are short-sighted, long-sighted or have blurry vision. This presents a challenge in the layout of the website. The contents of the website should be made to be legible by all these types of users, yet they all have different problems. Also, there are other users whose vision is okay and wish to get more styling of the web pages. All these challenges have to be considered by the portal.

Secondly, all humans do not have the same body features, in other words, they are differently ‘built'. There are those with chubby fingers, others have very small fingers, others have missing fingers. Fingers in this context refer to the capability to enter new data into systems or execute some commands. The real challenge comes when users are accessing the portal from touchscreen devices. Minuscule buttons will prove difficult to the users with big thumbs and fingers as they will not be able to interact comfortably with the system. Placing very big buttons in the portal will seem senseless to the users who have fingers that can comfortably interact with small buttons.

Under technical capabilities, some users are tech savvy thus they know a lot about online systems, how to interact with them and so on. Also, other patients have had minimal or no interaction at all with an online system. The challenge becomes designing a system that can accommodate for those who do not have experiences with such kinds of systems and at the same time not inconvenient those who already have the knowledge.

Challenges present in designing for providers with varying needs and technical capabilities

The providers of health care also have varying physical needs and technical abilities. To start off, under physical abilities, these caregivers have different ergonomic characteristics. They have different eyesight, cognitive capabilities, and mobility skills among others. These challenges directly affect the design of the interface of the web portal. Considerations will have to be made for all physical factors of the providers to ensure that they can comfortably interact with the system and accomplish the tasks they set out to do.

Under technical capabilities, some of these providers are well aware of online portals, some need just a small assistance, and they move on while some need total assistance to be able to perform their first few tasks. This challenges the system to provide an interface simple enough to be operated by a novice yet sophisticated enough to handle all the required functionalities. If unaddressed, a wrongly designed interface might introduce the gulf of execution problem. This is the difference that comes from user actions believed to attain a particular goal and the actions that the system allows. A user can get tangled in an infinite loop of steps without getting any worthwhile results.

Also under technical capabilities, the portal has many functionalities.These are to support the roles of each of the providers. This means that the menu or navigation offered by the portal has to be well organized so as not to be cluttered and introduce difficulties to everyone trying to use the portal. Also, the textual content will have to be replaced or paired with icons to help the providers access their roles quickly. This calls for the use of metaphors of the outside world to represent actions of the vendors. The challenge is choosing the appropriate metaphor known by all the diverse users.

List of some of the rules of engagement and how to overcome design challenges as part of developing shared patient-provider tools

Rules of engagement for patients as users

Patients will have to subscribe to some rules to use the portal well and contribute to its general success. First of all, it will be mandatory for all patients to have an enrolled record by a medical practitioner. This will help prevent the creation of needless files as it would have been if it was the users who were given that responsibility. Secondly, patients will only have one record. There is no need of one patient having redundant files as this becomes complicated to update and leads to inconsistencies in the database. Thirdly, only patients will be allowed to add, edit or delete their primal data in the records. This prevents attempts by any healthcare provider to change these records mischievously unfruitful. Fourthly, data entered by practitioners about patients will not be able to be manipulated by the patient. Lastly, patients will only be able to access their records online from the portal and see all the documents related to their interactions with the various health care providers. If these simple rules are followed, a simple correctly working portal will be maintained and also the security of the application and user information will be guaranteed.


Rules of engagement for the provider

Health care providers will have to stick to some rules that govern the correct and allowed the use of the portal. First of all, the providers will be required to register for an account with the web portal. They will be the only users of the portal that will create accounts for themselves reason being that they are smaller in number and more manageable. Secondly, each provider will only be allowed to create one account, any further attempts under the same details will be automatically rejected. This is to prevent redundancy that later on leads to inaccuracy and inconsistency of data. Thirdly, it is only providers that will be able to enroll patients in their registered accounts. Fourthly, providers will have the ability to enter information about patients such as the progress of care, medication or diagnostic data. This is to enable data entry of correct data because if this task was left to patients, lots of incorrect and misleading information would be entered. Lastly, only providers will be able to edit records that they have entered and also in reverse, providers shall not be able to edit records that have been entered by patients. This is to prevent data fabrication on both ends, the patient's side and the provider's side. If these rules are adhered to, the system will run correctly and efficiently.

How to overcome these challenges as part of developing patient-provider tools

Overcome for patients

To overcome the design challenges faced by users, some rules have to be followed to ensure that a system is developed that they can all use despite any physical or technical know-how shortcomings. First of all concerns the physical challenges. The first group of targets in physical challenges are those with eye problems. To be able to develop a system that can accommodate different eyesight capabilities of the users, it should be able to change aspects of its content to suit the user. Therefore, the portal will have some options to change the font sizes of the website hence allowing the user to adjust the site to his/her preferences.

The second physical challenge was about the finger size of the users; the system will be developed using standard sized buttons. These are neither too small to inconvenience the users with chubby fingers, and neither are they too big such that they occupy most of the white space and have negative impacts on the appearance of the website. The portal will also adjust according to user device screen size and therefore, it will be responsive.

Under technical challenges, the system will be able to offer useful information to all users regarding its use. Mandatory fields will be indicated, focus texts will be shown when a user hovers over functionality, sample values will be given to users, placeholders will be used in input boxes to show users the expectations of that particular field. In short, almost everything will be explained in a technologically wise way such that only novice users can see that helping content while expert users do not invoke such content.


Overcome for providers.

Under physical challenges facing providers, some of the mentioned ones were eyesight, cognitive capabilities, and mobility capabilities. The sight problem has already found a solution to having the option of changing font sizes of the contents. Under cognitive capacities, the portal will be built using flat user interface colors that boast of being the most attractive and legible colors. Therefore, providers will have no problem at all reading content from the portal. Under mobility capabilities, the portal will feature voice command support for providers who do not have hands to interact with the system.

Conclusion

Under technical challenges, the first one was about not being able to use the portal for the first task. To support this, a brief tutorial will automatically play after opening the portal that will clearly show provides ways in which they can interact with the system. Also, supportive text such as hover texts and placeholders will be all over the portal to assist the users in knowing what they are expected to do. The second technical challenge was about the use of icons as metaphors. The icons had to be metaphors of the real world that all the providers would understand. Therefore, the portal will have icons metaphorical to a hospital set up. Other universal metaphors will also be incorporated such as a pencil to indicate “edit” and a trash can indicate “delete”. The use of well-known symbols and images is going to help in getting providers a feeling of being sort of used to the system. 

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: "https://hubpages.com/privacy-policy#gdpr"

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)