True! I doubt people are using this sort of site to be constructive or courageous, though. I think they just want to vent. I can understand that. What I don't really understand is why anyone else is interested in reading that venting.
Here's my little vent: "EMPLOYEES LEAVE MANAGERS, NOT COMPANIES"
People do leave bad managers, but they also leave bad companies even if they themselves have a good manager.
yes! So many people are missing out on using claude-code directly on their knowledge base locally. Once you have it all local it seems completely crazy to push all of that context into a locked-in saas platform with mediocre AI tools.
I'm glad I completed my bachelor's before ChatGPT existed. Now in my master's program, I find myself increasingly dependent on AI. It's gotten to a point where professors grade using AI, so no brain-to-brain exchange is happening — just AI to AI.
I would also like to know. The German government actually has a decent API for accessing countless parliamentary documents, but it doesn't make the data very accessible to normal people...
I like the gateway concept as an alternative to opening the firewall. Are there any plans to add FHIR compatibility, for integrating with other FHIR systems?
> I like the gateway concept as an alternative to opening the firewall.
Cheers, it was a real revelation when we worked out how to do it!
> Are there any plans to add FHIR compatibility, for integrating with other FHIR systems?
We've definitely looked at such standards and systems but they seem to be targeted towards EHR data exchange and we are explicitly not an EHR. Our target is structuring research and research clinical data. The summary tool at the end of each instrument is designed to produce reports which can be fed into classic digital paper style EHRs where real clinical record keeping is required.
Not utilizing FHIR b/c you think EHRs will (a) consume your proprietary reports, and (b) be a downstream data system seems a big footgun. Additionally, while FHIR isn’t quite right for many research use cases, there are ongoing efforts such as mCODE [0], that use FHIR as a base because it is not proprietary and highly specified.
Maybe your EDC has other awesome characteristics. Based on the interest I’ve seen the FHIR ingestion of REDCap [1] is a winner for research nurse efficiency.
Right now, we're building first to address the needs of our institution, there's no FHIR enabled software there, and the clinicians make a direct request to generate reports for ingestion into their existing EHR system, so we oblige.
Interoperability is on our roadmap.
Meanwhile, we don't consider RedCap a competitor, the old-school LAMP stack is showing its age, and its "closed source" by most interpretations, including a hostile position on external developers.
We welcome contributions to accelerate FHIR support.
Oh, I forgot another aspect of FHIR, SMART on FHIR EHR integrations so the clinical research folks can optionally go straight in from the EHR.
I can’t say I disagree with your assessment of REDCap’s base tech except that it works sufficiently well to have pretty broad adoption, which can be approximated by the number of local endpoints exposed in their EHR-internal client record. A single institution project is certainly not a competitor and I wish y’all good fortune in ever getting beyond your patrons.
