OpenHIE Architecture Call - Monday, March 9 at 10:00 a.m. EDT

Just a reminder that we will be having the OpenHIE Architecture call Monday, May 9 at 10:00 a.m. EDT. Please note the new time. Also remember that Daylight Saving Time begins on Sunday, March 8th and may affect the time in which you dial into the call.

1. Diagram updates - (Jennifer 15 minutes)

2. Testing - (Carl 35 min)

3. AOB

We will be using Zoom:

Join from PC, Mac, Linux, iOS or Android :

Or Telephone : Dial: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)

Meeting ID: 832 179 402

International numbers available :

1 Like

If you could not join us for the OpenHIE Architecture call today, you can read the minutes or listen to the recording on 2020-03-09 Architecture Call wiki page.

The next OpenHIE Architecture call is scheduled for 10:00 a.m. EDT on Friday, March 27th.

1 Like

Michelle, thank you for posting the notes. I saw in them that someone is “Working on the creation of a matching framework - 2 use cases - a client is in the client registry …”. The Project Unify people are also looking at such a task, and coordination makes a lot of sense. Who should we contact about this effort? Thanks! -Eric Jahn

@eric I would reach out to @carl and include @sgrannis @jennifer.e.shivers

Hi @eric

Thanks for reaching out here, I think the notes are a little misleading in the discussion topic there. The section refers to the testing and compliance framework that we as an OHIE community are developing to support tools to validate themselves as OHIE compliant. The line in the notes refers to the point that the CR architectural spec has a set of defined interoperability workflows and functionality requirements and that we need to have test scenarios and various cases to test the ability of a tool to comply to these.

As a question how is project unity framing their interoperability test cases and I’d be happy to have teams collaborate on this with us as we try to build this out.


1 Like

Thank you for clarifying! Yes, can you identify the individuals we should coordinate with, on the matching framework test cases? We haven’t reached that point yet, as we’ve just completed the basic use cases and are looking to finish the sequence diagrams, APIs, etc. soon. But I think early communication between our groups should help us to arrive at products the other team can use. -Eric

Eric Jahn
Data Architect/IT Director
Alexandria Consulting LLC
St. Petersburg, Florida