When: 09/18/2014 at 11:00 AM EDT
Where: Google Hangout
Participants:
Recorded Video:
Agenda:
- Updates from the recent OHIE Architecture Meeting and how it pertains to the facility registry community (5 min)
- Identification and prioritization of FR workflows to support. A few to get us started as identified from implementers ... How can a FR consume code sets and hierarchy metadata from a trusted source? How can a tool contribute updates to a FR? What about more complex governance patterns for how facility registry data is managed? (~40 min)
- Gauge interest for an "Implementers Call" to pair with this technical call (5 min)
- AOB? (Remaining time)
Outcomes:
Reviewing the workflow process
Identify a need
Clarify sponsors and core actors
Depict as workflows
Identification and prioritization of FR workflows to support. A few to get us started as identified from implementers ... How can a FR consume code sets and hierarchy metadata from a trusted source? How can a tool contribute updates to a FR? What about more complex governance patterns for how facility registry data is managed? (~40 min)
Codesets to a FR …. services, facility type, administrative hierarchy (+++++
Patterns … Updates to a FR directly or from some existing source (++++
Updating the facility list in the data warehouse via a FR (++
Can a Facility Registry consume Provider Data and vice Versa (CSD?) (+
Some others to consider:
- Alerts? (Sometimes FRs need to be an index)
- Survey Tool consumers a FR or vice versa
Scenarios of Data Use:
Gauge interest for an "Implementers Call" to pair with this technical call (5 min)
Would be of value
AOB? (Remaining time)