| Table of Contents |
|---|
...
- AD - Admin Distribution
- PD - Patient Discovery
- DQ - Document Query
- DR - Document Retrieve
- DS - Document Submission
- DDS - Document Data Submission (Pilot)
- X12 - Core X12
- Direct - Direct Core
- admingui - Administrative GUI *.WAR, and the corresponding web services into the compiled *.EAR.
- was - Enterprise Application Archive (EAR ) for websphere application server
- weblogic - Enterprise Application Archive (EAR ) for weblogic application server
- jboss7 - Enterprise Application Archive (EAR ) for Jboss EAP 7 and wildfly application server.
How can I switch from MySQL to Oracle database?
...
NHIN does not call for cross-HIE authentication. Instead, you authenticate your users locally however you choose, then "assert" the authentication info (who is the user, why they are requesting data, etc.) and pass this in the entity assertion class, which gets represented in the NHIN message as a SAML token. The receiving gateway then uses its own policies to determine if it will allow for this call.
What mechanism is NHIN using for identifying the Patients?
Each organization can identify its patients how it chooses. When you share patient data, you communicate the patient identifiers using a qualified patient id (local patient id + a globally unique assigning authority).
We are looking to integrate CONNECT into our solution by leveraging reports from other agencies, analyze them and compare them to our reports. Is there any suggestions on how to set up and configure the adapter for this system?
NHIN currently provide two mechanisms for collecting clinical data: a real time query for data (provided by "doc query" and "doc retrieve") and an async pub/sub model (provided by HIEM).
The way things look to be evolving on the NHIN specification factory (the group that makes the specs for NHIN) is that HIEM will contain sub-specs to detail for what you can issue subscriptions, called a profile. At the moment, the only thing that you are really "allowed" to subscribe for is a "consumer preference profile" (document containing the rules about who can see a "my" data). The next soon-to-be-released profile spec is for GIPSE, which covers subscriptions/notifications that contain aggregated data, expected to be used for groups like CDC collecting data from public health agencies (think: "how many people had the flu yesterday").
I want to enable my CONNECT to "grab" medical data from existing EMR systems like OpenMRS or OSCAR. Which service of CONNECT should I use?
To enable your CONNECT to "grab" medical data from an existing EMR you would probably use 3 services:
- Patient Discovery - A NHIN service to query nodes on the NHIN for information on patient's based on demographics.
- Document Query - A NHIN service to query nodes on the NHIN for metadata relating to documents about a specific patient
- Document Retrieve - A NHIN service to retrieve documents from nodes on the NHIN.
...
I want to enable my CONNECT to "grab" medical data from existing EMR systems like OpenMRS or OSCAR. Which service of CONNECT should I use?
To enable your CONNECT to "grab" medical data from an existing EMR you would probably use 3 services:
- Patient Discovery - A NHIN service to query nodes on the NHIN for information on patient's based on demographics.
- Document Query - A NHIN service to query nodes on the NHIN for metadata relating to documents about a specific patient
- Document Retrieve - A NHIN service to retrieve documents from nodes on the NHIN.
In order to use these services, you would write an adapter which integrates with these productions or depending on these product's capabilities, maybe create services in OpenMRS, OSCAR, or some integration tool which provision the adapter interface for each of these services. Then when CONNECT receives one of these requests over the NHIN, CONNECT will call your services and the EMR can respond in turn.
We are looking to integrate CONNECT into our solution by leveraging reports from other agencies, analyze them and compare them to our reports. Is there any suggestions on how to set up and configure the adapter for this system?
NHIN currently provide two mechanisms for collecting clinical data: a real time query for data (provided by "doc query" and "doc retrieve") and an async pub/sub model (provided by HIEM).
The way things look to be evolving on the NHIN specification factory (the group that makes the specs for NHIN) is that HIEM will contain sub-specs to detail for what you can issue subscriptions, called a profile. At the moment, the only thing that you are really "allowed" to subscribe for is a "consumer preference profile" (document containing the rules about who can see a "my" data). The next soon-to-be-released profile spec is for GIPSE, which covers subscriptions/notifications that contain aggregated data, expected to be used for groups like CDC collecting data from public health agencies (think: "how many people had the flu yesterday").
What mechanism is NHIN using for identifying the Patients?
Each organization can identify its patients how it chooses. When you share patient data, you communicate the patient identifiers using a qualified patient id (local patient id + a globally unique assigning authority).