Exchange Service | Description |
|---|---|
Patient Discovery | Locate patients based on demographic information |
| Patient Location Query | Locate communities that may have information about a requested patient |
Query for Documents | Locate electronic health information, represented by documents, associated with a specific patient that conforms to a set of query criteria |
Retrieve Documents | Retrieve specific electronic health information as documents associated with a subject |
Document Submission | Submit patient-specific documents when they become available without the need for a request or query |
| Document Data Submission (Pilot) | Submit document metadata without the need to submit the entire document binaries |
Administrative Distribution | Submit non-patient-specific documents when they become available without the need for a request or query |
| Core X12 Document Submission | Submit patient-specific administrative documents when they become available without the need for a request or query |
| Feature | Description |
|---|---|
| Fan Out | Sends a given payload to all known exchanges when no targeted exchange is specified. This feature is for Patient Discovery and Document Query only. |
| Policy Engine | Provides means for access restriction for services and patient information. |
| Event / Transaction Logging | Provides logging of various events such service invocation, layer invocation, and service failure. |
| Audit Logging | ATNA compliant logging of service invocation. |
| Exchange Targeting | Specify a payload for one or more NHIN target communities. CONNECT will then send the payload to each specified target |
| Admin GUI | Optional GUI with web services for managing and configuring a deployed CONNECT instance. |
| Direct | Securely exchange health information via email to other trusted providers. |
| Database-less deployment | Allows community to deploy CONNECT, in passthrough mode, without any databases. |
| Configurable Web Service Registry | CONNECT can download web service registry from both UDDI and FHIR STU3 compliant directory. |
| KeepAlive and Custom HttpHeaders | CONNECT can be configured to add Keep-Alive headers to all outgoing requests or on a single request as indicated by assertion block in entity message. |