When: 01/09/2014 at 11:00 AM EDT
Where: Google Hangout
Participants: Bob Jolliffe, Carl Leitner, Martin Verzilli, Eduardo Jezierski, Scott Teesdale
Recorded Video: http://www.youtube.com/watch?v=bfs3uBRqNsI
Agenda:
- Coordinate IHE - CSD Connect-a-thon Preparations
- Generate and Discuss 2014 Goals re: FRED API and Facility Registry Implementations
- AOB? Feel free to join and suggest it as an agenda item.
Notes:
Services in CSD
The service directory entry just shows OIDs
So what do they mean?
Services are basically code lists with a coded type underneath
Then you go to the code list to see what they are.
This allows multiple code sets to be shared.
What are we actually going to do at the connectathon?
Choreograph a bit
We have IP addresses and tables.
What is going to happen? Watch the video from IHE prep materials to learn more...
How will the bootstrapping occur? Pull Facilities from RM for example?
We will have to use the dataset with a list of facilities that they expect us to be providing. Those are the data points where we need to be consistent.
We will confine ourselves to the sample data. No need to do more initially
Are we planning to carry a couple virtual machines?
After a test run it is possible that there will be an info-man with some level of data in it? Do you start with a new info-man or re-use the old one?
It can handle multiple directories. It is easy enough to have 2 info-mans
Perhaps could be helpful, will determine during a dry run
Moving Forward with Test Data
- Lets get these in place in RM so that they can start pulling these things
- Service Directory: https://github.com/his-interop/openinfoman/tree/master/resources/service_directories
Carl is putting this data into the
Is there an example test suite for the connect-a-thon?
We can ask Lyn
They will probably ask us to create 1-2 facilities with these properties
Can we do a dry run online?
Lets try to do it together…will help to identify issues
Before the next OHIE-FR meeting.
Scott will send out details to participants
Risks for CSD?
CSD is still a malleable thing?
The changes for the SOAP request we will
They are flexible so it is ok if we make a change?
It is currently a trial implementation and not a final text
They do have Profiles that have been in trial implementation for 3 years that have architecture around it
Doesn’t think the preliminary fact of text will hold up architecture considerations
CP for Names
Pending need
Change the name
Seems that the sample
Contact Points Included?
Lyn has the person data
You can also link to provider OID and not provide that data?
Does Not appear we are testing against it
Unfortunate but you might not know who this person really is
We have people but we don’t have provider IDs
Other Facility Registry - Potential Goals
- We wanted to send a community survey to get feedback
- Demonstration days - groups and teams
- Share lessons learned from the field
- End of March to April … lets take all the lessons learned and give a rev to whatever APIs
- Other Suggestions or Thoughts for the FR community moving forward?