Connect Drchrono and OpenFEC
Describe what you want to happen between Drchrono and OpenFEC in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Drchrono
263 documented operations. See all Drchrono operations
- POSTCreate a task
/api/tasks - POSTCreate messages in doctor's message center
/api/messages - POSTCreate a new appointment or break on doctor's calendar
/api/appointments - POSTCreate sub-vendors - When you get orders
/api/sublabs - POSTCreate lab tests. An example lab workflow is as following: - When
/api/lab_tests - POSTCreate patient amendments to a patient's clinical records
/api/amendments
OpenFEC
91 documented operations. See all OpenFEC operations
- GETCombines the election and reporting dates with Commission meetings
/calendar-dates/ - GETSearch legal documents by document type
/legal/search/ - GETList elections by cycle, office, state, and district
/elections/search/ - GETSchedule E covers the line item expenditures
/schedules/schedule_e/ - GETAll official records and reports filed by or delivered to the FEC
/filings/ - GETBasic information about electronic files coming into the FEC
/efile/filings/
How a Drchrono and OpenFEC automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Drchrono and OpenFEC, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Drchrono and OData for namespace microsoft.graph11,675 operations
- OData for namespace microsoft.graph and OpenFEC11,503 operations
- Cloudflare and Drchrono3,385 operations
- Cloudflare and OpenFEC3,213 operations
- Drchrono and NetBox1,107 operations
- NetBox and OpenFEC935 operations
- Drchrono and GitHub1,074 operations
- GitHub and OpenFEC902 operations
- Drchrono and Mist1,031 operations
- Mist and OpenFEC859 operations
Questions about connecting Drchrono and OpenFEC
- Can Drchrono connect with OpenFEC?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Drchrono to OpenFEC?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Drchrono and OpenFEC?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Drchrono and OpenFEC?
- Drchrono publishes 263 documented operations and OpenFEC publishes 91. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Drchrono or OpenFEC is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Drchrono and OpenFEC. Descriptions are each provider’s own words, not ours.