Discussions

I’m not sure if we are supposed to respond to these but here is what I think. First, I think we have to stop thinking about the technical problem and solutions. The technology works. The first problem to be solved is “who do you trust to connect the person’s security credential to their personal records”. In this model, the insurer may do it. In other models the provider (practice or hospital) may do it. If the personal record is that of a multi-stakeholder HIE, I think both can do it. Anyone is essence can be a registration authority so long as the fabric of trust is there.

We are preparing to release the software for Alpha testing next week. To
that effect we are doing the following:

1. Prepare Alpha Testing packet
2. Identify and Coordinate with Alpha Test sites
3. Edit routines to put in regulatory text
4. Create and test distributable install files.

Sam

Good Morning:

I would like to volunteer for the program committee. I attended the last conference and found it to be informative.

Sharon Mc Neill

3904 Brenbrook Drive

Randallstown, Md 21133

From: Apache [mailto:apache@groups.osehra.org] On Behalf Of Conrad Clyburn
Sent: Monday, December 10, 2012 5:26 PM
To: HEALTHBOARD
Subject: [healthboard] 2nd Annual OSEHRA Open Source EHR Summit and Workshop... Save the Date ...

Just wanted to let you know, in the wake of our XINDEX tests, I had to fix
I bug I didn't quite introduce but rather unmasked.

The INIT routines produced by DIFROM were larger than 15000 characters,
even though the maximum is 15000. After a couple of hours of debugging, it
turns out that the counting code was faulty: it didn't count new line
characters!