Patient and Population Services API Registration
Interoperability Requirements
The implementation of Standardized API for patient and population services opens the opportunity for third-party developers to access NeoMed EHR patients and practices data.
In order to meet ONC interoperability requirements, NeoDeck Holdings, NeoMed’s parent company uses Dynamic Health IT Dynamic FHIR® API as relied-upon software.
Registration
Interested developers need to email the following information to NeoDeck’s Customer Service department at cs@nd-soft.com and confirm the Terms of Service agreement. Ensure to fill out all fields.
Information | Type or Select Option |
---|---|
Company | |
|
|
|
|
|
|
|
|
|
|
Developer | |
|
|
|
|
|
|
|
|
Client App Name |
|
App Type |
|
| |
EHR Launch Scopes |
|
Default OAuth 2.0 Flow for Patient and Provider Apps |
|
Default OAuth 2.0 Flow for System Apps |
|
App URL |
|
Redirect URI's |
|
Redirect URI's |
|
Redirect URI's |
|
PostLogoutRedirectURIs |
|
FHIR Resource Scopes Required |
|
Identity Scopes Required |
|
External Identity Provider (IdP) |
|
Version of FHIR Resources |
|
Links to Documentation
NeoDeck Holdings FHIR® Server - 4.0.1: Home Page (patientvault.com)
FHIR API Documentation: ApiDocumentation (patientvault.com)