| Table of Contents |
|---|
Build:
Can CONNECT be used for Carequality implementation?
CONNECT is not currently designed for Carequality exchange.
Where is the CONNECT source code repository?
...
- 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 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. As I said earlier its 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.
Can CONNECT be used for Carequality implementation?
...
.
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
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
What is the limit on length of an HCID/OID?
There is no limit to the length of an ISO OID. Some standards, such as DICOM, have declared an arbitrary length limit of 64 characters, so if you wish to use the OID you are registering in such a standard, you should try to conform to those other restrictions. HL7 does not put any restriction on the length of an OID, but the website software cannot accept an ‘External’ OID longer than 128 characters at this time.
For more information, please see FAQ from HL7: https://wiki.hl7.org/index.php?title=HL7_OID_Registry_Frequently_Asked_Questions
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:
...
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/HOKSAMLAssertionBuilder.java & gov/hhs/fha/nhinc/callback/openSAML/CallbackMapPropertiesOpenSAML2ComponentBuilder.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/HOKSAMLAssertionBuilder.java & gov/hhs/fha/nhinc/callback/openSAML/OpenSAML2ComponentBuilder.java
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
What is the limit on length of an HCID/OID?
There is no limit to the length of an ISO OID. Some standards, such as DICOM, have declared an arbitrary length limit of 64 characters, so if you wish to use the OID you are registering in such a standard, you should try to conform to those other restrictions. HL7 does not put any restriction on the length of an OID, but the website software cannot accept an ‘External’ OID longer than 128 characters at this time.
For more information, please see FAQ from HL7: https://wiki.hl7.org/index.php?title=HL7_OID_Registry_Frequently_Asked_Questions
General:
What are the different layers of CONNECT, and how are they used?
...