honeymoose
/
hapi-fhir
mirror of https://github.com/hapifhir/hapi-fhir.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add modelconfig toggle

This commit is contained in:
Tadgh 2021-03-30 12:57:09 -04:00
parent 419a5829ea
commit 02e6514176
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
hapi-fhir-jpaserver-model/src/main/java/ca/uhn/fhir/jpa/model/entity/ModelConfig.java
View File

@ -99,6 +99,7 @@ public class ModelConfig {
private Map<String, Set<String>> myTypeToAutoVersionReferenceAtPaths = Collections.emptyMap();
private boolean myRespectVersionsForSearchIncludes;
private boolean myIndexOnContainedResources = false;
private boolean myAllowMdmExpansion = false;
/**
* Constructor
@ -159,6 +160,24 @@ public class ModelConfig {
return myAllowContainsSearches;
}
/**
* If enabled, the server will support the use of :mdm search parameter qualifier on Reference Search Parameters.
* This Parameter Qualifier is HAPI-specific, and not defined anywhere in the FHIR specification. Using this qualifier
* will result in an MDM expansion being done on the reference, which will expand the search scope. For example, if Patient/1
* is MDM-matched to Patient/2 and you execute the search:
* Observation?subject:mdm=Patient/1 , you will receive observations for both Patient/1 and Patient/2.
* <p>
* Default is <code>false</code>
* </p>
* @since 5.4.0
*/
public boolean isAllowMdmExpansion() {
return myAllowMdmExpansion;
}
public void setAllowMdmExpansion(boolean theAllowMdmExpansion) {
myAllowMdmExpansion = theAllowMdmExpansion;
}
/**
* If enabled, the server will support the use of :contains searches,
* which are helpful but can have adverse effects on performance.