Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
A package to help with FHIR searching when needed search parameters are not available
A Python package to support FHIR Searching in contexts where needed search parameters are not supported
NOTE: Currently, the only option for capability_statement_file is 'epic_r4_metadata_edited.json'
from fhirsearchhelper import run_fhir_query
# This is using objects to store search params
output: Bundle | None = run_fhir_query(base_url='https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4/', query_headers={'Authorization': 'Bearer 1234567'}, resource_type='Patient', search_params={'resourceType': 'Patient', 'search_params': {'name': 'Smith', 'deceased': 'true'}}, capability_statement_file='epic_r4_metadata_edited.json')
# This is using a raw query
output: Bundle | None = run_fhir_query(query_headers={'Authorization': 'Bearer 1234567'}, query='https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4/Patient?name=Smith&deceased=true', capability_statement_file='epic_r4_metadata_edited.json')
FHIRSearchHelper performs some data transformation when retrieving data from Epic to handle potential upstream data processing issues.
To support NLP of documents, all DocumentReferences that are retrieved that contain URLs that reference a Binary resource where the document text is stored, are "expanded" by retrieving that Binary resource and inserting the content into the DocumentReference.content field of the resource. If one of the attachment types is text/html and text/plain is not also present, the HTML is converted into base64-encoded plain-text for easier upstream NLP operations, without removing existing data.
All MedicationRequests that are retrieved that contain medicationReferences instead of medicationCodeableConcepts are "expanded" by retrieving the referenced Medication resource and inserting the codes of that resource into MedicationRequest.medicationCodeableConcept, and removing MedicationRequest.medicationReference.
All Conditions that are retieved that have a Condition.category.code of encounter-diagnosis and do not have Condition.onsetDateTime, are "expanded" by retrieving the referenced Encounter in Condition.encounter and setting Condition.onsetDateTime to Encounter.period.start to indicate the beginning of a Condition. If there is no referenced Encounter or the referenced Encounter does not have a period, the onsetDateTime is set to 9999-12-31
.
In their current form, CapabilityStatement
s do not have a way to express when a search parameter for a resource is conditionally accepted. For example, in the Epic R4 CapabilityStatement
, for the Condition
resource, there exists a listed search parameter of code
. In the description, there is a note that this search parameter is only accepted when the category
is equal to infection
. The only way that this conditional information would be known is by manual reading of the description. To alleviate this issue, and to avoid extreme custom handling in this package, currently you must edit the CapabilityStatement
of any server with which you would like to use this package and add custom extensions to the search parameter. Keeping with the above example of the search parameter code
for the Condition
resource, here is what the CapabilityStatement.rest[0].resource.where(type = 'Condition').searchParam.where(name = 'code')
element looks like:
{
"name": "code",
"type": "token",
"documentation": "Search for Conditions with a specified code. This is only used when searching for infections.",
"extension": [
{
"url": "true-when",
"valueString": "category==infection"
}
]
}
Here we have added an extension with a url of true-when
that is a machine readable statement denoting when a search parameter is accepted by the server. It currently only supports == to show equality and in to show membership of a list (e.g. "category in [infection, health-problem]"). This also works for when a search parameter is limited in the values it will successfully search for. For example, here is what the CapabilityStatement.rest[0].resource.where(type = 'Condition').searchParam.where(name = 'category')
element looks like:
{
"name": "category",
"type": "token",
"documentation": "Search for Condition resources by category.",
"extension": [
{
"url": "true-when",
"valueString": "category in [dental-finding, encounter-diagnosis, genomics, health-concern, infection, medical-history, problem-list-item, reason-for-visit]"
}
]
}
FAQs
A package to help with FHIR searching when needed search parameters are not available
We found that fhirsearchhelper demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.