{"id":15406,"date":"2022-07-01T17:21:39","date_gmt":"2022-07-01T21:21:13","guid":{"rendered":"https:\/\/www.elderplan.org\/?page_id=15406"},"modified":"2025-11-19T15:15:58","modified_gmt":"2025-11-19T20:15:58","slug":"interoperability-for-developers","status":"publish","type":"page","link":"https:\/\/www.elderplan.org\/es\/interoperability-for-developers\/","title":{"rendered":"Elderplan Interoperability Third-Party Application Developer User Guide"},"content":{"rendered":"\n
\n
\n

Overview<\/h2>\n\n\n\n

Application developers who want to enter the health care interoperability space need to abide by strict standards to keep member data private and secure.  <\/p>\n\n\n\n

Elderplan Interoperability APIs are developer-friendly, standards-based APIs that enable 3rd<\/sup> party application vendors to connect their application programs to access Elderplan data.<\/p>\n\n\n\n

This document provides an overview of how to register 3rd<\/sup> party applications to connect to the Elderplan FHIR server and access member data.<\/p>\n\n\n\n

The OnyxOS Developer Portal enables third-party developers to register, manage, and connect their applications securely to Elderplan APIs in compliance with CMS interoperability standards.<\/p>\n\n\n\n

<\/p>\n\n\n\n

1. Developer Registration<\/h2>\n\n\n\n

For this initial step, an organization account should exist in the portal system under which its members and agents register.<\/p>\n\n\n\n

To register as a member, developers can go to https:\/\/portal.safhir.io\/<\/a> and submit their details. User details will be reviewed, approved, and appropriate permissions will be assigned.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

2. Developer Access Request<\/h2>\n\n\n\n

After the developer registers and their details are reviewed and activated by the portal administrator, they will be able to log into the portal. Once the member account is created, activated on the backend, and phone verification is successfully completed, the member can access the portal to manage their applications.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

3. Create an application request<\/h2>\n\n\n\n

A successful login lands on the developer homepage, where the developer can create a new application request software by submitting details.  To create a new application:<\/p>\n\n\n\n

1. Click on create new application button.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

2. Enter the Application details<\/strong>. <\/p>\n\n\n\n

The Mandatory fields are: Name, Application ID, Application Version, Application Type, Redirect URIs.<\/p>\n\n\n\n

The optional fields are: Logo URI, Application Description.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

3. Enter the client details. <\/p>\n\n\n\n

The mandatory fields are: Client URI, Client Terms of Service URI, Client Policy URI, Client Contacts, Support Email, Support Phone Number. <\/p>\n\n\n\n

The optional field is: Security Certifications and Attestations URI.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

4. Select \u201cTEST Elderplan \u2013 STG\u201d as the data provider from the drop-down menu, then click Submit Access Request. Please ensure the applicable implementation guides are selected. (mandatory step)<\/p>\n\n\n\n

NOTE \u2013 If the developer selects Test and Production environments at this time, know that ONLY the Test environment will be approved to allow for thorough testing and review prior to the access to the Elderplan Production environment.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

5. Once the request is submitted, a success page will appear marking the completion of application creation. The Elderplan Administrator will review and approve the application within 3 to 5 business days. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

4. Payer Admin review and approve the access request<\/h2>\n\n\n\n

After receiving a notification about a new request, a Payer Admin logs into the portal and sees the list of software vendors requesting access to Payers they have approval permissions for.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

5. Application credentials gets generated<\/h2>\n\n\n\n

In this step, the payer admin approves the request after reviewing the application details. The approval action also triggers a registration process in the backend which goes out to the Payer tenant, registers the application, and retrieves the registration credentials.  These credentials will later be used to authenticate with the Payer when attempting to retrieve data.<\/p>\n\n\n\n

The credentials generated include client_id and client_sec.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

6. Developer receives the notification of approval<\/h2>\n\n\n\n

Once the application is approved by the Payer Admin, the developer who submitted the approval request will be notified via email.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

7. Developer accesses approved application request to retrieve credentials<\/h2>\n\n\n\n

The developer who submitted the request can then log in to the portal and retrieve the generated credentials that will be used to authenticate their app with the Payer.<\/p>\n\n\n\n

<\/p>\n\n\n\n

8. Screenshots<\/h2>\n\n\n\n

Pending Approval Section<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Approved Section<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Rejected Section<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Revoked Section<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Support Contact Details<\/h2>\n\n\n\n

If you\u2019re facing any issues related to application registration, developers account username\/password, or OIDC connection issues with test\/sandbox\/prod etc., please send us an email with details. We\u2019ll connect and resolve the issues ASAP (if issue is related to Elderplan FHIR server).<\/p>\n\n\n\n

Support Email ID:  apisupport@mjhs.org<\/a><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Overview Application developers who want to enter the health care interoperability space need to abide by strict standards to keep member data private and secure.   Elderplan Interoperability APIs are developer-friendly, […]<\/p>\n","protected":false},"author":20,"featured_media":0,"parent":0,"menu_order":28,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"categories":[],"class_list":["post-15406","page","type-page","status-publish","hentry"],"translation":{"provider":"WPGlobus","version":"3.0.2","language":"es","enabled_languages":["en","es","zh"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"es":{"title":false,"content":false,"excerpt":false},"zh":{"title":false,"content":false,"excerpt":false}}},"acf":[],"jetpack_sharing_enabled":true,"publishpress_future_action":{"enabled":false,"date":"2026-04-14 04:52:11","action":"change-status","newStatus":"draft","terms":[],"taxonomy":"category","extraData":[]},"publishpress_future_workflow_manual_trigger":{"enabledWorkflows":[]},"_links":{"self":[{"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/pages\/15406","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/comments?post=15406"}],"version-history":[{"count":0,"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/pages\/15406\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/media?parent=15406"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.elderplan.org\/es\/wp-json\/wp\/v2\/categories?post=15406"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}