Home / Technical research / ECP
Platform research
ECP technical research.
Available source documents and verified published identifiers, with source-file and page citations. Product versions, components, release labels, and compatibility requirements retain their original context.
Sources reviewed
01 / Source documents
The materials behind the research.
Links open the publisher’s source. The document type and review status distinguish full files from web pages or landing pages.
Technical document · HTML
ECP API Developer Resources
Reviewed web snapshot
Public detailed vendor integration reference; webhook events, payload schemas, OAuth client credentials, REST methods, scopes and care-charting constraints. Real access requires approved integration partnership. URL /clinical/v1 is API path version, not product release or hotfix.
View original source : ECP API Developer Resources (opens in a new tab)Reviewed source file
10_ECP/Technical_Documents/ECP_API_Developer_Resources_49f38ad4_web_snapshot.htmlWhite paper landing page · HTML
ECP vs SNF Software White Paper
Reviewed landing page; full paper not downloaded
Vendor explicitly labeled whitepaper; public comparison summary. Full paper requires a form request and was not reviewed; classify as buying/comparison paper rather than system architecture.
View original source : ECP vs SNF Software White Paper (opens in a new tab)Reviewed source file
10_ECP/Whitepapers/ECP_vs_SNF_Software_White_Paper_c1c99155_web_snapshot.htmlWhite paper landing page · HTML
ECP vs Property Management Software White Paper
Reviewed landing page; full paper not downloaded
Official whitepaper landing page; public workflow/comparison summary, not release or patch reference.
View original source : ECP vs Property Management Software White Paper (opens in a new tab)Reviewed source file
10_ECP/Whitepapers/ECP_vs_Property_Management_Software_White_Paper_cde82888_web_snapshot.html
02 / Verified identifiers
Published labels, with their source context.
These findings establish what appears in the reviewed documents. They do not establish the latest release or any organization’s installed version, build, or applicable hotfix.
No ECP product version, build number, or hotfix number was verified from the reviewed source files. The available documents are listed above; specific evidence gaps appear below.
03 / Research limits
What the documents do not establish.
- No ECP product version verified in downloaded files.
- No ECP build number verified in downloaded files.
- No ECP hotfix identifier verified in downloaded files.
- API documentation and two public whitepaper landing pages contain no established ECP software release/build/hotfix identifiers.
Page numbers refer to the physical pages in the reviewed PDF; printed page labels are shown where available. Web and JSON sources are unpaginated and cited by section. Publisher files and web pages may change after the review date. Research coverage reflects the available documents and does not imply vendor endorsement.
Assess the records in context.
Tell us the platform and the records available so we can discuss an assessment scope.
Paid engagements. Scope and fees agreed before review.