<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://healthcommentary.org/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://healthcommentary.org/public/?>

<MySmartChannels Public="true" UserID="177899" dT="48" t0="1227272868363">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>198420</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Patient Advocacy">182415</OwnerID>
        <CreatedByID ObjectClass="User" Title="plarson">183236</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="plarson">183236</ModifiedByID>
        <CreateTime Title="2008-02-28 14:46:19 EST">1204227979492</CreateTime>
        <ModifyTime Title="2008-02-28 14:58:30 EST">1204228710439</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Dossia: Under-visioned</Name>
        <Summary>New service moves in the right direction, but is still a long way from lifespan planning</Summary>
        <Description>&lt;p&gt;I was asked recently by an MBA student to give my impressions of &lt;a title="Dossia" href="www.dossia.org"&gt;Dossia&lt;/a&gt;.&lt;img style="WIDTH: 197px; HEIGHT: 98px" height="98" hspace="0" src="http://www.firstpointpr.com/dossia.jpg/dossia-full.jpg" width="197" align="right" border="0" /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;br /&gt;&amp;nbsp;&lt;br /&gt;What is Dossia? In&amp;nbsp;its own words: &amp;quot;The Dossia Founders Group is a consortium of large employers united in their goal of providing employees, their dependents, retirees and others in their communities with an independent, lifelong health record. Dossia founders are funding Dossia, an independent secure, non-profit infrastructure for gathering and securely storing information for lifelong health records. At the request of employees and other eligible individuals, Dossia gathers health data from multiple sources. Employee participation as a Dossia user is completely voluntary and individuals have complete control over who sees their information.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;Once gathered and securely stored in a decentralized database, the health information is continually updated and is available to individuals for life even if they change employers, insurers, or doctors. The Dossia Founders Group includes AT&amp;amp;T, Applied Materials, BP America, Inc., Cardinal Health, Intel Corporation, Pitney Bowes, sanofi-aventis and Wal-Mart. The Dossia project has been endorsed by the American Academy of Pediatrics, the American Academy of Family Physicians, the Centers for Disease Control and Prevention and the National Association of Manufacturers. The Dossia Founders Group will work with Children's Hospital Boston and other qualified and experienced vendors to develop and implement the Dossia Network infrastructure.&amp;quot;&lt;br /&gt;&amp;nbsp;&lt;br /&gt;Here's my take:&lt;br /&gt;&amp;nbsp;&lt;br /&gt;1. Dossia recognizes &amp;quot;Lifelong Record&amp;quot; but never grasps the power of using the tool as a forward-looking planning instrument. They are still imagining this as a relative backward facing passive repository of information -- an organizer, if you will -- that could help eliminate waste and inefficiency and potentially decrease health care costs.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;2. They recognize the potential mine field between employer and employee here, and go to some lengths to ensure firewall protection of sensitive employee health records. Specifically they say that the employer and the insurer will not (at least for now) have access to the information, and that data security will be paramount.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;3. The founders state as their motivation the creation of&amp;nbsp; &amp;quot;a new kind of health care benefit for their employees, dependents and retirees.&amp;quot; That reflects the mindset here -- that employers will provide the leadership to transform American health care. This is not unreasonable since they are at considerable financial risk in the United States&amp;nbsp;because of employer based health insurance. But it's useful to keep in mind that we are the only developed nation on the planet with an &lt;a href="http://www.healthpolitics.org/program_transcript.asp?p=empbasedhc_two"&gt;employer-based health care system&lt;/a&gt;. My point - that it is reasonable to ask where best to base an initiative like this, since (as here) the funders do color the solution proposed.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;4. The medical collaborators are heavy hitters -- Children's Hospital (in Boston), Harvard and MIT. These have been at the forefront of HIT (Health Information Technology) for several decades. Their own weakness is that they are huge academic hospital health systems with the biases that this entails -- toward hospital and provider based solutions versus consumer based. Big health technology vendors like Intel, GE, Phillips and Siemens have traditionally focused on these big players to sell them machines like CAT scanners and MRI's, and chips to run these machines. It's natural that they would therefore turn to these same institutional partners for information solutions.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;5. The corporations involved are contributing not only financial resources, but also access to their employee bases to test out the application, as well as serve as a potential customer base for new products and applications that integrate with Dossia as they are developed. The employee bases (certainly decoded and protected) could also in the future be accessed for research and development.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;6. Key features emphasized are that the application is &amp;quot;personally controllable, private and portable&amp;quot; -- again the notion of a &amp;quot;container for disparate medical information&amp;quot; that will stay with the consumer wherever he or she is. Again no concept of this as a planning tool, nor discussion of integration of other planning health data (nutrition, exercise, reproductive planning, educational objectives, financial planning, housing needs, etc.) Thus the product is &amp;quot;medicalized&amp;quot; and supports institutions primarily as the data sources versus individuals as data sources within &lt;a href="http://www.spencerbooks.com/"&gt;a holistic, home-based framework&lt;/a&gt;.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;7. Dossia does have the &lt;a title="AAFP" href="http://www.aafp.org/online/en/home/publications/news/news-now/professional-issues/20060522medicalhome.html%20"&gt;endorsement of the AAFP&lt;/a&gt;&amp;nbsp;&lt;a href="http://and/"&gt;and&lt;/a&gt; the &lt;a title="AAP" href="http://www.aap.org/advocacy/archives/julymedhome.htm"&gt;AAP&lt;/a&gt;, &lt;a href="http://both/"&gt;both&lt;/a&gt; of whom have endorsed the &amp;quot;Medical Home&amp;quot; concept.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;8. Governance of the non-profit involves current &lt;a href="http://www.dossia.org/founders/dossia_leadership/"&gt;employees of the sponsoring companies&lt;/a&gt;. (Colin Evans,director of the Systems Software Lab at Intel serves as President of the non-profit, and Michael Critelli, Executive Chairman of Pitney Bowes is Chairman of the Board of Dossia).&lt;br /&gt;&amp;nbsp;&lt;br /&gt;9. Dossia is committed to an &amp;quot;open platform&amp;quot; design. In doing this they are leaning toward enhanced compatibility and usability of the product, and suggesting that this will be non-proprietary and used in the public interest.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;10. Why Wal-Mart? Several reasons. First, &lt;a href="http://www.usatoday.com/money/industries/insurance/2007-09-18-walmart-health_N.htm"&gt;it improves their reputation in health care&lt;/a&gt; where they've been criticized in the past, and offers their employees a additional health benefit at low cost to them.&amp;nbsp; Second, the intent is to have this open platform spur development of a range of compatible products, and those have to be sold somewhere. Third, health care is a high transactional space, and involvement with patients creates floor traffic. Wal-Mart, in hosting &lt;a href="http://walmartstores.com/GlobalWMStoresWeb/navigate.do?catg=707&amp;contId=6440"&gt;other health related activities and products&lt;/a&gt;&lt;a href="http://%20now/"&gt; now&lt;/a&gt; and the build-out of a better medicial record, has the opportunity to leverage these activities to increase sales.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;Summary: Dossia got the name (Lifelong Record) right, but has yet to absorb fully the concept. The &lt;a href="http://www.healthpolitics.org/program_transcript.asp?p=your_health_future"&gt;Lifespan Planning Record&lt;/a&gt; (LPR) is unique because it is fundamentally an integrated planning tool, that could be customized and individualized by consumers and their families to support better decision making, enhanced adherence to agreed upon plans, and incremental adjustment of behaviors to improve health outcomes. The goal? Not simply allowing an individual to construct a better health care record, but to empower individuals to reach their full human potential. And the design and graphic interface of the LPR must be so engaging, such a pleasure to use, so &amp;quot;sticky&amp;quot;&amp;nbsp; (integrating photos, videos, diary entries, personal hallmarks, individual research and breakthrough insights), that it will engender high customer loyality (as an electronic product) and support consumer driven (as opposed to employer driven) viral marketing.&lt;/p&gt;&lt;p&gt;One last item: Today's headline on page 1D of the &lt;a title="Wall Street Journal" href="http://biz.yahoo.com/wallstreet/080228/sb120416090319398335_id.html?.v=2"&gt;Wall Street Journal&lt;/a&gt;&amp;nbsp;reads, 'Google to offer health records on the Web:Tech Giant Joins Effort To Prod Consumers To Keep Their Data in Portable Electronic Profiles.'&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>lifespan planning record</Keyword>

                 <Keyword>Mike Magee</Keyword>

                 <Keyword>patient advocacy</Keyword>

       </Keywords>

      </CommonProperties>

               <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                <ns3:Collection name="Byline" type="urn:MyST-Technology.Structured.Collection.Captyx.Custom.Byline">
                 <ns3:Attribute name="Byline" type="text" value="By Mike Magee, MD"/>

                 <ns3:Attribute name="_captyx.position" type="text" value="_top"/>

                 <ns3:Attribute name="_captyx.embargo" type="checkbox" value="false"/>

                 <ns3:Attribute name="_captyx.scope" type="text"/>

                 <ns3:Attribute name="_captyx.sortkey" type="text"/>

       </ns3:Collection>

      </ns3:Details>

               <RemoteInfo>
                <UserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; (R1 1.5); .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)</UserAgent>

                <RemoteHost>127.0.0.1</RemoteHost>

                <RemoteAddr>127.0.0.1</RemoteAddr>

                <RemoteUser>plarson</RemoteUser>

                <ForwardedFor>68.60.235.104</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
        </ContentDocument>
       </Resource>
       <Shares/>
       <Subjects/>
       <UserPermissions>
        <CanDelete>false</CanDelete>
        <CanDiscover>true</CanDiscover>
        <CanEdit>false</CanEdit>
        <CanEditPermissions>false</CanEditPermissions>
        <CanRead>true</CanRead>
       </UserPermissions>
       <CommentInfo>
        <CommentChannelRef AllowAnonymous="true" Inherited="true">
         <ChannelID ObjectClass="Channel" Title="[Public] Public Comments">179654</ChannelID>
         <UserPermissions>
          <CanCreateChannelItem>false</CanCreateChannelItem>
          <CanDelete>false</CanDelete>
          <CanDiscover>true</CanDiscover>
          <CanEdit>false</CanEdit>
          <CanEditPermissions>false</CanEditPermissions>
          <CanPublish>false</CanPublish>
          <CanRead>true</CanRead>
         </UserPermissions>
        </CommentChannelRef>
        <Comments>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>198430</ObjectID>
            <ObjectClass>Resource</ObjectClass>
            <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">179654</OwnerID>
            <CreatedByID ObjectClass="User" Title="$Anonymous">173239</CreatedByID>
            <ModifiedByID ObjectClass="User" Title="plarson">183236</ModifiedByID>
            <CreateTime Title="2008-02-28 16:47:43 EST">1204235263468</CreateTime>
            <ModifyTime Title="2008-02-29 09:37:06 EST">1204295826860</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>Undervisioned?  Maybe, But It's Fixable</Name>
            <Summary/>
            <Description>&lt;p&gt;Mike,&amp;nbsp;&amp;nbsp; Thanks for a great explanation and commentary.&lt;/p&gt;&lt;p&gt;While you might be right about Dossia being limiited in not being a visionary lifetime record, I don't see anything in the Dossia model that would limit it's future expansion to what you describe.&amp;nbsp; You gotta start somewhere -- v9 will be better than v1.&lt;/p&gt;</Description>
            <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
            <ContentType>application/xml</ContentType>
            <ContentDocument>
             <ItemProperties>
                   <CommonProperties>
       
                   <Hidden>false</Hidden>
            </CommonProperties>

                  <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                   <ns3:Collection name="Vince Kuraitis" type="urn:MyST-Technology.Structured.Collection.Contact">
                    <ns3:Attribute name="EMail" type="email" value="vincek@bhtinfo.com"/>

                    <ns3:Attribute name="Web" type="url" value="http://e-CareManagement.com"/>

       </ns3:Collection>

      </ns3:Details>

                  <RemoteInfo>
                   <UserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)</UserAgent>

                   <RemoteHost>127.0.0.1</RemoteHost>

                   <RemoteAddr>127.0.0.1</RemoteAddr>

                   <ForwardedFor>24.119.23.246</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
           </ContentDocument>
          </Resource>
          <UserPermissions>
           <CanDelete>false</CanDelete>
           <CanDiscover>true</CanDiscover>
           <CanEdit>false</CanEdit>
           <CanEditPermissions>false</CanEditPermissions>
           <CanRead>true</CanRead>
          </UserPermissions>
          <CommentInfo>
           <CommentChannelRef>
            <ChannelID/>
           </CommentChannelRef>
           <Comments/>
          </CommentInfo>
         </Item>
        </Comment>
        <Comment>
         <Item>
          <Resource>
           <ObjectID>198478</ObjectID>
           <ObjectClass>Resource</ObjectClass>
           <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">179654</OwnerID>
           <CreatedByID ObjectClass="User" Title="plarson">183236</CreatedByID>
           <ModifiedByID ObjectClass="User" Title="plarson">183236</ModifiedByID>
           <CreateTime Title="2008-02-29 10:40:45 EST">1204299645584</CreateTime>
           <ModifyTime Title="2008-02-29 10:40:45 EST">1204299645584</ModifyTime>
           <SecurityModel>Controlled</SecurityModel>
           <Name>Need to Avoid Technology Segregation</Name>
           <Summary>If we address issues early, new technology will bring us together</Summary>
           <Description>Vince-&lt;br /&gt;&amp;nbsp;&lt;br /&gt;You're absolutely right about this -- that v9 will be better than v1, and we must start somewhere. My only concern is that the pace of change is accelerating, and if our vision is underpowered we could easily end up with technology segregating the people from the people caring for the people, rather then connecting them in a meaningful way. As we can see from the Google announcement this week, there is a logic of launching lifetime planning records off of an open consumer platform, with the expectation that we caregivers will move to the people rather than the other way around. The advantages include compatibility, speed of implementation and elimination of many of the financial and organizational obstacles that have slowed us down in the past. Were we to create the expectation that, for individuals to be insured, consumers would have to first establish their LPR (as one of the responsibilities that come with universal coverage) we might tip this whole system quite rapidly.&lt;br /&gt;&amp;nbsp;&lt;br /&gt;Mike Magee</Description>
           <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
           <ContentType>application/xml</ContentType>
           <ContentDocument>
            <ItemProperties>
                  <CommonProperties>
                   <Hidden>false</Hidden>

      </CommonProperties>

                  <RemoteInfo>
                   <UserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; (R1 1.5); .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)</UserAgent>

                   <RemoteHost>127.0.0.1</RemoteHost>

                   <RemoteAddr>127.0.0.1</RemoteAddr>

                   <RemoteUser>plarson</RemoteUser>

                   <ForwardedFor>68.60.235.104</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
           </ContentDocument>
          </Resource>
          <UserPermissions>
           <CanDelete>false</CanDelete>
           <CanDiscover>true</CanDiscover>
           <CanEdit>false</CanEdit>
           <CanEditPermissions>false</CanEditPermissions>
           <CanRead>true</CanRead>
          </UserPermissions>
          <CommentInfo>
           <CommentChannelRef>
            <ChannelID/>
           </CommentChannelRef>
           <Comments/>
          </CommentInfo>
         </Item>
        </Comment>
       </Comments>
      </CommentInfo>
      <Views>
       <SourceID ObjectClass="Channel" Title="[Weblog] Patient Advocacy">182415</SourceID>

              <View>
               <Name>blog</Name>

               <Model>blogsite/HealthCommentary/web</Model>

               <Style/>

               <Scheme/>

       </View>

      </Views>
       <Views>
        <SourceID ObjectClass="Channel" Shared="true" Title="[Public] Dr. Mike Magee's BLOG">177931</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/HealthCommentary/my-whatsnew</Model>

                <Style/>

                <Scheme/>

       </View>

      </Views>
       </Item>
      </GetChannelItem_Result>
     </MySmartChannels>
