tag:blogger.com,1999:blog-4384692836709903146.post444447905660122655..comments2024-03-18T04:38:01.678-07:00Comments on Dispatch from the Digital Health Frontier: Next Steps for Health Information Exchange in MassachusettsJohn Halamkahttp://www.blogger.com/profile/04550236129132159307noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4384692836709903146.post-10445428745300560472011-09-21T07:40:08.484-07:002011-09-21T07:40:08.484-07:00John, thanks for sharing this MA plan. I'm cur...John, thanks for sharing this MA plan. I'm curious about the sequencing of capabilities for 2013 vs 2014. I would have thought that using a "pull" pattern there would be Record Locators and Repositories and that some data would be "mined" from those records to support analytics. But since you have databases and analytics before pull, it implies that the data is probably mined from "push" transactions. Did you have in mind HISPs that not only route Direct Messages but also store them and mine them? Generally in Direct Project, that was not viewed as the role of a HISP, because they would be "opening the envelopes" and additional consent issues would be raised that Direct doesn't explicitly address. Or were you thinking of "push" in the form of HL7 messages rather than Direct Project? <br />Thanks,<br />DavidDavidhttps://www.blogger.com/profile/13251393010554964308noreply@blogger.com