<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Betty Davis on Medium]]></title>
        <description><![CDATA[Stories by Betty Davis on Medium]]></description>
        <link>https://medium.com/@bettyad7?source=rss-1c94d6a1342b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*daeOt_Rh6y9OAWvkBa8cvA.jpeg</url>
            <title>Stories by Betty Davis on Medium</title>
            <link>https://medium.com/@bettyad7?source=rss-1c94d6a1342b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:53:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bettyad7/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Entir: a mobile app that helps manage your health records]]></title>
            <link>https://medium.com/@bettyad7/entir-ux-design-for-a-health-information-management-application-2f8f76ff7fc4?source=rss-1c94d6a1342b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f8f76ff7fc4</guid>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Betty Davis]]></dc:creator>
            <pubDate>Mon, 18 Jun 2018 03:39:56 GMT</pubDate>
            <atom:updated>2019-12-21T01:05:59.417Z</atom:updated>
            <content:encoded><![CDATA[<p>My UX Design journey building a mobile app prototype from scratch</p><figure><img alt="Mobile phones with prototype screens" src="https://cdn-images-1.medium.com/max/908/1*1624FPnZdXLCL6NjjK1bcg.png" /></figure><p><strong>I am drawn to projects that can help improve people’s lives</strong>. Having myself “managed” a chronic condition throughout my lifetime and moving from one country to another, many of my health records were lost and my health information became inaccessible.</p><p><strong>I lacked ownership of my health history and records, </strong>something that I could have strongly leveraged to <strong>gain insights </strong>and better manage my health condition.</p><p>While conducting research and as I talked with people about the app, <strong>I realized that many people faced similar challenges: almost every person mentioned having an issue, either with their data/records being out of their hands, or being unable to track or access their information within a reasonable timeframe and ease.</strong></p><p>In some cases, people were having <strong>issues accessing their records from another country, others needed certain information like immunization records for travel and experienced difficulties obtaining them</strong>. Some were <strong>overwhelmed</strong> by the amount of information they had to manage; for example, one of our respondents wanted help managing an elderly parent’s health information.</p><h3><strong>Potential challenge</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6CgFkmXjdij6RXXo." /><figcaption>Photo by NordWood Themes on Unsplash</figcaption></figure><p>We started with the <strong>hypothesis</strong> that in the US* people aren’t provided with helpful management tools to own their medical records, and therefore they lack a comprehensive and accurate health picture of their medical history and activity. *<em>This could also apply to other countries</em></p><p><strong>For context:</strong> in the US, if a patient visits a Primary Care Physician (PCP) in a hospital, the patient’s information, i.e., treatment records will stay in that hospital. If they decide to see a different doctor or go to a different hospital, it is likely that the <strong>medical information will not transfer:</strong> sometimes the systems will not talk to each other, and a patient’s information becomes inaccessible. Sometimes medical offices aren’t equipped with the technology. <strong>Ultimately, the information and records keeping burden fall on the patient.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fpPJ3r1PAJ-L3rsd." /></figure><h4>It is a heavy administrative and cognitive burden that many patients must carry by not having immediate and complete access to their life&#39;s health history and records. People can answer questions about their recent history, but they have limited detailed insights into their life-long health history and patterns.</h4><h3><strong>Potential Solution</strong></h3><p>Broadly, I thought of an application that could <strong>enable ownership </strong>of medical activity, data and records; keeping track of <strong>a person’s hospital &amp; doctor activity chronologically throughout their lifetime </strong><em>(hospital and doctor activity means: listing all hospitals/health providers visited, prescriptions taken, doctor visits, treatment plans, diagnosis, vaccinations, and lab work) </em><strong><em>in real-time.</em></strong> Presenting to the patient a comprehensive view of their <strong>entire life’s health information and activity; all packaged in a seamless, minimalist interface</strong>.</p><h3><strong>Panning for gold — need-finding through competitive assessment, surveys, and interviews</strong></h3><p>Like panning for gold, that is how it felt to me. At times respondents won’t say much, and that’s ok, but <strong>sometimes we get a glimpse into their personal and very particular situation and the challenges they face, and that’s where the real value is — in continuously asking unbiased, open-ended questions, and finding ways to observe how people behave and how can we help them overcome their challenges.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PZDJQP0ELGh3wE77." /><figcaption>“Two people holding cups of coffee while seated opposite to each other at a round table” by <a href="https://unsplash.com/@theexplorerdad?utm_source=medium&amp;utm_medium=referral">Joshua Ness</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We planned and conducted an <strong>online survey, phone/online interviews to learn more about how people manage their medical information</strong>, existing concerns, “moments of joy/delight”, and challenges they faced. We defined what information we wanted to learn from participants. I drafted a set of questions and used <em>Typeform</em> to conduct the survey.</p><p><strong>One of the challenges I faced was getting people to fill out the survey, and even more important, to have a variety of participants. I decided to post my survey on Reddit, </strong>and with a little guidance from channel managers, I was able to post the survey on the right channel, which yielded more responses.</p><h3>The Survey Speaks…</h3><p>From our survey results, we learned that most of our respondents (<strong>females between the ages of 31–40) </strong>tend not to check or pay attention to their medical records, some of the reasons are: few medical visits per year, that their medical office does not offer an online service, or it’s too difficult or not engaging enough to access. Other details include:</p><ul><li><strong>40%</strong> of our 33 respondents had zero to one medical visits per year</li><li><strong>35%</strong> had used an online platform to access their medical records</li><li>What respondents <strong>liked most</strong> about online health platform: <strong>convenience</strong>, what they<strong> liked least</strong>: <strong>look and feel</strong></li><li>Records usually managed or tracked: <strong>Medical visits, lab results, vaccines, and prescriptions</strong></li><li>How do people keep their records: <strong>35%</strong> hard copy, <strong>29%</strong> don’t keep them, <strong>24%</strong> use a digital app</li></ul><h3>Survey participants were asked what they like or dislike about the way they currently manage their personal health records, they said…</h3><ul><li><strong>“I can’t remember where they [health records] are, I think at my parents&#39; house</strong>. <strong>It’s not a good system.”</strong></li><li>“I like the concept of keeping medical records accessible in a mobile app where I can download in case I switch providers. <strong>I do not have my medical records from the first 22 years of my life because they were not easy to access, and I have a serious undiagnosed issue that would be great to explain with testing results and doc notes,</strong> <strong>but I would have to call those providers which is inconvenient.”</strong></li><li>“<strong>It’s hard to keep track of all of my physical papers, but some of them are from before the days of online portals</strong>, and I haven’t taken the time to scan them in.”</li><li>“I’m pretty organized with my records … I like the fact that if I’m at home I can easily access them. But I’d love to bring at least some of them with me, every day. <strong>I suffer from diverse and severe food allergies that have to be monitored on a daily basis. The test record is quite long and I cannot bring it with me all the time.</strong>”</li><li>“<strong>Privacy</strong> concerns, <strong>transferring data</strong> from one doctor to another, <strong>crappy experience online</strong>”</li></ul><h3>❤ listening to people: face to face chats</h3><p>I got to listen to participants’ challenges, frustrations, gaps, moments of joy, and their future vision of the topic. People were very sensitive<strong> </strong>at times about their roadblocks because the issue is so close to them. It helps to be a good listener, to have empathy, and be curious.</p><p>I facilitated a <strong>session that was welcoming </strong>and put together an<strong> interview script </strong>that would allow participants to share more about their behaviors without leading them. <strong>Listening, pausing, and allowing participants to speak and probing them when needed</strong>. Also checking myself to make sure that I was staying impartial and neutral.</p><p>Here’s what in-person interviewees were saying:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3uuyJZannHcGgjDSVo8Gpw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3KI0Rw70p72v5P-DWg0gkw.png" /></figure><blockquote>At the end of the questions, the interviewees were also asked for future- looking perspectives: <strong>how will health information management and apps will look in 10 years?</strong> <strong>Answers ranged from gamification, to fully-digital interactions, to sensors that live in cups or toilets tracking the latest data from their users.</strong></blockquote><h4>What I personally learned as I conducted interviews</h4><p>Coming from a visual design background I understand the importance of a well-laid-out interface, but a <strong>customer-centric approach</strong> — that is the strongest foundation to build upon.</p><p>It is truly valuable and healthy to take the time to talk with users because you get a <strong>closer look at people’s experiences of joy, frustration, and sentiment on the topic. Without talking to users/customers, the product is built completely on assumptions, which will end up causing waste.</strong></p><h4>Word of advice before conducting user interviews</h4><ul><li>I learned the <strong>importance of knowing your tools</strong> and deciding which tools work best for what. For example, it can be overrated to video chat (I experienced technical issues from both my end and my interviewee’s end), a regular phone call could be the solution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m8mGPNTG5sarJAwU." /><figcaption>Access the entire research brief here</figcaption></figure><ul><li>It is also good to respect the interviewee’s time: <strong>arrive and end on time, being prepared by having an alternate path to communicate in case the technology malfunctions.</strong></li><li><strong>If possible, record your interviews, it’s good to hear each participant’s voice and lingo, it can help when building personas, additionally it is more reassuring to have a recording than relying solely on your notes. </strong>You can record with Google hangouts and Youtube (at first, it can take some time to set-up and I highly recommend a practice run). If you are doing a regular phone call, <strong>ACR is a free call recorder for Android</strong> that does the job.</li></ul><p><strong>It was also very helpful to define what I wanted to learn from my interviewees </strong>by drafting a script with non-leading, probing questions.</p><p>Here is a <a href="https://docs.google.com/document/d/1clZOJe3q0xUsMD34cEgobr-DHXBBY07lxCsvW34D-DU/edit?usp=sharing">link to the script</a> for reference.</p><h3>Competitive Assessment</h3><p>We put together <strong>a competitive assessment </strong>of existing health information and health data management products (that were used by our survey respondents) with the goal to better understand what offerings are already out there and their features. We made an inventory of each product to learn features in detail. We assessed Apple health, Google health, Lifelog, My health online, and Health Vault. <a href="https://docs.google.com/presentation/d/10aFoLWmA9MernAXfqjV1_Go-UsCD2DD9k_ntGDnn7uQ/edit?usp=sharing">See the competitive assessment brief here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E7GUlt3N2MxauFzlLgMdtQ.png" /><figcaption><a href="https://docs.google.com/presentation/d/10aFoLWmA9MernAXfqjV1_Go-UsCD2DD9k_ntGDnn7uQ/edit?usp=sharing">See the competitive assessment brief here</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJNqQb0g7yLCisfwUsNahQ.png" /><figcaption><a href="https://docs.google.com/spreadsheets/d/1mQwRtIzRxpwm43CoEJcg69JokO5HuxugLEl4AkPyHw0/edit#gid=0">See the feature inventory here</a></figcaption></figure><h3>Assembling Personas</h3><p>From talking to people, I stitched together three potential personas: <strong>Stella </strong>the <strong>College Student and Freelancer</strong>, <strong>Chris</strong> the <strong>Traveling</strong> <strong>Consultant </strong>and <strong>Mary</strong> the <strong>Working Mama Bear</strong>. I kept going back to my interview notes and survey data to search for challenges and goals, I started matching them up, and personas started to come together. In a nutshell, here they are:</p><p><strong>Chris the traveling Consultant</strong>- a type A personality who wants his information seamlessly accessible “yesterday” and is a fan of good health, stats, tracking, and tech trends. He is always on the move and needs quick and easy access to his health data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZhBU6QREAMjE0WOO_-C1A.png" /><figcaption>Persona of Chris the Traveling Consultant</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-kuGwTByZXxvIciagxwXxA.png" /><figcaption>Empathy map for Chris,the traveling consultant</figcaption></figure><p><strong>Stella the Student and Freelancer-</strong> a busy student/freelancer who switched to Obamacare, and switched Doctors too. She visits different doctors depending on her coverage. She’s busy and can use some help knowing and keeping her health information. She suffers from severe food allergies.</p><figure><img alt="Stella the college student and freelance writer persona" src="https://cdn-images-1.medium.com/max/1024/1*PAQYIZKewf-pQ_cgaJ6QPw.png" /><figcaption>Persona- Stella the college student</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETLHHaCxtQ2fnlXGl8IHNw.png" /><figcaption>Empathy map- Stella the college student</figcaption></figure><p><strong>Mary the Working Mama Bear</strong>- she has a lot on her plate with work and family (children &amp; elders) and is disorganized with her health information- she stashes all in a folder and stresses out later. She missed giving her elderly mother a post-surgery medication, causing a delay in her recovery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MK13zEh1inmRQkzro6ErMA.png" /><figcaption>Persona for Mary the mama bear working full time</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bN2snUrUsDkMIP04GDr7g.png" /><figcaption>Empathy map for Mary the working mama bear working full time</figcaption></figure><h3>The basics: Minimum Viable Product (MVP) and User Stories</h3><p><strong>User stories </strong>are very helpful in defining the MVP, because we now have a refined list of the tasks that users would potentially perform on the application. <a href="https://twitter.com/andretweeting">My mentor</a> and I looked at the list together and decided which features made more sense to prioritize, all this keeping in mind the interviews, personas, empathy maps, and scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tyLRIeM6gUf7HSvHQiPC8A.png" /><figcaption><a href="https://docs.google.com/spreadsheets/d/1OcFywRNcak_9jKLMfZuDxWX2kLYCk6C5_3ugxP2Aiw4/edit?usp=sharing">See the complete spreadsheet here</a></figcaption></figure><p>I learned that it is <strong>important to keep referring to the user stories as we build the prototype</strong>. It is also good to keep referring to the personas, empathy maps, and scenarios. For this project I used <strong>google spreadsheets, </strong>this application facilitated sharing, feedback, and editing.</p><h3>Preparing for construction: Information architecture</h3><p>I decided to do an <strong>online card sort</strong> because it was fast, easy to carry around (especially if visiting local coffee shops) easy to share with remote users, and convenient for me as a researcher to quickly get results and accurate visualizations of the data. I used <strong>Optimal Workshop</strong> for the task.</p><p>I headed to my local coffee shop, bought $5 dls gift cards. I put up a sign “Free small coffee for 15 mins of your time” — <strong>it was a morning during a weekend and I got the participants I needed within a couple of hours.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UmxXUutqqw2ak1C6." /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Participants had to pass a mini-screen</strong>: they were asked if they managed their own health records and if they used a certain kind of technology to manage their health records, and if they were fluent in English.</p><p>When completing the cardsort, <strong>most participants were able to easily understand and sort out all described features</strong>, with an average time of 4.87 min. to complete. <strong>Some of the challenges were:</strong> repeated words that meant the same thing i.e., physician and doctor.</p><h3>Sketching, Wireframing and Prototyping fun!</h3><p>As a visual designer and artist — I love to draw (I auction my drawings for charity at Movimiento de Arte y Cultura Latino Americana) this was the part of the process I was looking forward to.</p><p><strong>Until this point, I had only been talking about my idea/concept.</strong> Some folks that I talked to got it, but others still had a question mark hovering over their heads. <strong>It was great to pour-out the idea onto a piece of paper. I started seeing what was missing — what made sense and what didn’t. </strong>The moment I presented the hand-drawn screens to my mentor I saw a change: he got it, right away. I could even sense the excitement. I got the same response from other viewers, they now had something tangible — they were able to quickly grasp the concept, relate to it and provide feedback or ask questions.</p><p>I was wondering if people would find value in the idea, and if they’d like it. I pushed myself to show it around, and was surprised to get a positive response, even from tough critics. Their interest reinforced value and purpose- it fueled my energy and passion for the idea.</p><p>Next, are the hand-drawn sketches. I used a dot pad and some markers. They were made in less than an hour. Questions and ideas started to surface in regard to the interaction, security, and information architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3QvVayrvsdphomQC8QQ_5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FMK-OY5_03QC6idXPd9JQ.png" /></figure><h3>Making the prototype digital</h3><p>After sketching out the screens, my mentor and I decided I could start building the digital version. We decided to use <strong>Marvel</strong> — I was completely new to the tool — but was able to pick it up fairly easy due to its intuitive, minimal interface. This was helpful, because it limited the number of visual embellishment options, focusing on the process/ interaction</p><p><a href="https://marvelapp.com/"><strong>Marvel</strong></a><strong> </strong>adds a ton of value because it provides a set of ready-to-use screens for either Android or iOS. That way the designer doesn’t have to focus on the style-guide/ design system too much and we can jump right into the interaction and build a working draft/prototype of the product that can be tested.</p><p>Here, <strong>I learned to check myself once more: </strong>It was tempting to think of more features, but I reminded myself to write ideas down, and only build the basics for the tasks that we carved out from our research so that the tasks could be ready to be tested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V3b1JuQodou8TXJ2Pud7SQ.png" /><figcaption>Prototype for testing only: <a href="https://marvelapp.com/bd5c8be">Entir prototype in Marvel</a></figcaption></figure><h3>Usability testing: In Nike’s words…Just do it</h3><p>Don’t delay it, just break the ice and start talking with people, the sooner you can get feedback, the better.</p><p>Armed with a brief intro of the product and a small list of tasks, I broke the ice to testing and put the prototype in someone’s hands. Best thing ever because <strong>I got to observe someone using the prototype, and immediately observe which areas had ease-of-use and which areas had challenges. </strong>I now had feedback to apply to the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O1b_mQfqS0dZ3F5Z." /><figcaption>Photo by Headway on Unsplash</figcaption></figure><p>In the first testing sessions, I wanted to see<strong> </strong>if the information made sense the way it was laid out, also wanted to perfect the script and tasks*, and wanted to see if people went to the hamburger menu (inactive at this point) vs. a menu I had placed under the profile picture. They went for the hamburger menu like it was a free giant cheeseburger, with zero calories.</p><h4>Lesson learned — Getting participants: Know the pond you’re fishing at</h4><p>I decided to run usability testing <strong>in the middle of the week at my local coffee shop: it has a good mix of parents, students, and professionals.</strong> My tools: a laptop, a brief screener, a research script with key tasks, a hand-sketched sign: “Free sm. Coffee for 15 mins of your time”, and a few gift cards. I placed my sign on a table and sat there…and waited….and waited…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xMsiEtxctivSe5Fk." /><figcaption>Photo by <a href="https://unsplash.com/@kaylamrojales?utm_source=medium&amp;utm_medium=referral">Kayla Rojales</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong><em>Weekend vs. middle-o-the-week people (in the SF Bay Area). </em></strong>I thought finding participants would be similar to my earlier weekend-research but I was wrong. <strong>In this case, testing in the middle of the week yielded fewer people willing to engage.</strong></p><h4>Check yourself some more</h4><p>Check that you aren’t leading your participants…it sounds easy, but there are many ways to do it. For me, it was <strong>resisting the urge to help participants- </strong>one of my testers was an elderly gentleman. He had a calm way of completing the tasks, and I caught myself thinking: <em>let me help him out</em>…but instead, I was patient, and in the end, he was able to figure things out.</p><p>Good to avoid <strong>using word-for-word naming </strong>when speaking out the tasks. This can also be <strong>leading, </strong>it’s <strong>better to use slightly different words than the ones used in the app.</strong></p><p>In the end, it was a rewarding experience to chat with real people, and seeing them interact with the product- it gave me insights I wouldn’t have been able to figure out myself, to mention a few:</p><ul><li>90% of users tended to go for the <strong>hamburger menu vs other menus.</strong></li><li>Participants wanting to be able to <strong>see their medical “homework” or “treatment plan/ medical next steps”.</strong></li><li>A participant who thought the <strong>“main profiles page” was confusing</strong> and <strong>unnecessary.</strong></li><li>A person suggesting to add a comment box for <strong>“reason for calling/symptoms” textbox before requesting to call a nurse.</strong></li></ul><p>It is a continuous process, and we will keep testing and improving the product.<strong> In the future, the app could help visualize and interpret a patient’s data and create a clear view of a person’s present status and future trends — unveiling patterns and predicting health outcomes.</strong></p><h3><strong>First visual guidelines and concepts</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bXH6HCYOSu7UmVJhF2oQWw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QyufeulJBS58LDxgm-Cl8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*tEZ31W6J5twZoGIcvIh_lA.png" /></figure><h3><strong>Latest screens of the prototype created with grommet.io components</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QV4G-pK2_EyWzS45mHULlg.png" /></figure><h3>Conclusion</h3><p>It has been great to take this journey and experience the strong value of the UX process: a user-centric and lean-approach.<strong> Talking with users, conducting research, and usability testing were some of the most valuable and enjoyable parts of the process. Great to see how much can be done and learned. It is good to stay curious and creative, to ask questions and be humble.</strong></p><p>Regardless of perceived wins or losses,<strong> you will strike gold in what you have learned.</strong></p><p>Note: This is a Work in Progress, there is more coming! I am creating a hi-fidelity “polished” prototype in Adobe XD…keep an eye out!</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f8f76ff7fc4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>