HUD-Data-Lab / Data.Exchange.and.Interoperability

Repository for Homeless Management Information System (HMIS) development and management of products to support data exchange and interoperability
GNU General Public License v3.0
2 stars 5 forks source link

Does this API solve the proposed use case? #4

Open eanders opened 3 months ago

eanders commented 3 months ago

I wanted to start a discussion around who would use this API and if it solves the CE Assessment use case proposed.

At the moment it doesn't include Coordinated Entry information (specifically assessments and events are not part of the spec) so it seems somewhat lacking for solving data sharing for coordinated entry.

Additionally, are there any examples of software that collect coordinated entry assessments that would use such an API to push back to HMIS? Or that might consume an HMIS API to augment their internal client/enrollment concept?

CindyNoeUSDS commented 3 months ago

Thanks @eanders, we do need to build out the solve for CE information, and I know @kaungst can propose some approaches to building out the reference so that it can address the use case, along with you and others in the group.

In terms of examples of software that collect CE assessments and would use such an API to push back to HMIS, we know that this is happening (and about to go live) for the Kent County CoC (they worked with WellSky to build out the CE to HMIS API), and we are in conversations with them about this example. We are also looking into potential use of APIs to push either full CE data or partial client data for intake in CoCs that partner with United Way and the 211 call center system to access social services in communities.

In general, we think this use case will be a helpful reference case to for how CoCs using a third party software to collect individual client information can push that to HMIS via API in a transactional, individual client level (rather than a bulk CSV transfer). Part of our task will be communicate and demonstrate the applicability of this reference to other use cases, beyond just coordinated entry.

kaungst commented 3 months ago

@eanders +1 to the current API spec not being enough to not support CE assessments in full. While we are looking at examples in other communities, would it be correct to say one we know works (albeit inefficiently) is the structure provided by the CSV format specification? I've held off on taking from the existing CSV format specs in favor of the community proposing an alternative.

Do you have any examples or recommendations for resources/endpoints that would achieve the CE assessment use case?

eanders commented 3 months ago

@kaungst thanks for adding the 1:1 parity with the HMIS CSV, I think that will help with the use case.

It looks like https://github.com/HUD-Data-Lab/Data.Exchange.and.Interoperability/issues/7 is covering the ability to find a client. Thanks!