| 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.
What is CONNECT's Source code branching strategy?
CONNECT is our “master” branch, developers commit code (by merging pull requests) into CONNECT_integration. The CI jobs then validate the commits and merge them into CONNECT. Therefore we know CONNECT will always build and be stable. This same process is repeated for all of the release branches (4.2/4.2_integration, 4.3/4.3_integration), however those branches don’t enjoy the same level of activity as the CONNECT/CONNECT_integration branches.
How can I switch from MySQL to Oracle database?
...
How can I switch from MySQL to Oracle database?
Follow the Steps below to run CONNECT Oracle Scripts for a fresh install:
1. Run dropall_oracle.sql
2. Run nhincdb_oracle.sql
3. Run populateTestData_oracle.sql
4. Run loadTestDocumentData_oracle.sql (Please Note: This script can't be run from SQL Plus due to line limitation, you have to use SQLDeveloper or some other COTS product like TOAD, PL/SQL Developer)
How do
...
CONNECT common type library is part of the CONNECT product suite and it caters the needs of the CONNECT product requirements. The main reason we put it in the maven repository is make our build easier and address the requirements that we support. It is specifically designed for CONNECT and may not address some of your requirements.
But you can always fork the source from GitHub and extend it to your needs. Also you can build your own extended library into your own private repository and reference it from there.
How do I configure my CONNECT TLS/SSL settings?
TLS settings are not configured via CONNECT but CONNECT does provide some TLS override features such as /wiki/spaces/CONNECTWIKI/pages/118035664
How do I customize Assertion AttributeStatements?
Currently only the the elements defined in the AssertionType (check NhincCommon.xsd schema) are supported. You can modify the source to add custom assertion attributes, below are the steps:
...
I configure my CONNECT TLS/SSL settings?
TLS settings are not configured via CONNECT but CONNECT does provide some TLS override features such as /wiki/spaces/CONNECTWIKI/pages/118035664
How do I customize Assertion AttributeStatements?
Currently only the the elements defined in the AssertionType (check NhincCommon.xsd schema) are supported. You can modify the source to add custom assertion attributes, below are the steps:
- Change the AssertionType in NhincCommon.xsd schema (Add a new element with name/value or any type based on your requirement)
- Generate Common Types and Connect WebServices jars
- Use the Common Types and Connect WebServices jars in CONNECT
- Add the respective getters in gov/hhs/fha/nhinc/callback/openSAML/CallbackMapProperties.java & CallbackProperties.java
- Extract the value from the entity and set it on the request context --> gov/hhs/fha/nhinc/saml/extraction/SamlTokenCreator.java
- Create the new Attribute (Attribute statement) that you need to pass to the other gateway --> gov/hhs/fha/nhinc/callback/openSAML/CallbackMapPropertiesHOKSAMLAssertionBuilder.java & CallbackProperties.javaExtract the value from the entity and set it on the request context --> gov/hhs/fha/nhinc/samlcallback/extractionopenSAML/SamlTokenCreatorOpenSAML2ComponentBuilder.javaCreate the new Attribute (Attribute statement) that you need to pass to the other gateway --> gov/hhs/fha/nhinc/callback/openSAML/HOKSAMLAssertionBuilder.java & gov/hhs/fha/nhinc/callback/openSAML/OpenSAML2ComponentBuilder.java
How do we change/add text to ED datatype in Java using CONNECTCommonTypesLib?
CONNECT common type library is part of the CONNECT product suite and it caters the needs of the CONNECT product requirements. The main reason we put it in the maven repository is make our build easier and address the requirements that we support. It is specifically designed for CONNECT and may not address some of your requirements.
But you can always fork the source from GitHub and extend it to your needs. Also, you can build your own extended library into your own private repository and reference it from there.
What is CONNECT's Source code branching strategy?
CONNECT is our “master” branch, developers commit code (by merging pull requests) into CONNECT_integration. The CI jobs then validate the commits and merge them into CONNECT. Therefore we know CONNECT will always build and be stable. This same process is repeated for all of the release branches (4.2/4.2_integration, 4.3/4.3_integration), however those branches don’t enjoy the same level of activity as the CONNECT/CONNECT_integration branches.
What is HCID/OID?
HCID is home community identification. HomeCommunityId is structured as an OID limited to 64 characters and specified in URI syntax. For example, the homeCommunityId of 1.2.3 would be formatted as urn:oid:1.2.3
...