Discussions

Is there an endpoint in the API to send single or multiple CCD, that provide us the same functionality as "settings>Patients>Import Patients" in the portal?

Good morning, I just saw that HealthGorilla was offering electronic ordering of COVID-19 testing via its API. Out of curiosity, would this be possible to employ as white-labeled within a separate app? Our mobile app services 60+ population with hospice care. We thought it would be, at this time, crucially helpful to embed this feature of yours within our app. If this is possible, can you describe next steps? Wishing you well, Trip Levine

HOW TO UPLOAD MEDICAL RECORDS THRU THE PORTAL

im trying to update an allergy created in the portal, when the PUT endpoint is called i receive the following error: { "resourceType": "OperationOutcome", "issue": [ { "severity": "error", "code": "processing", "diagnostics": "substance cannot be modified." } ] } The substance has not been modified, only a reaction has been added. I've tried to update the Allergy without modifying it (sending in the PUT the same data i receive in the GET), But i still receive the same error. Allergy to be updated: { "resourceType": "AllergyIntolerance", "id": "7023d85de188facfe5985755", "meta": { "versionId": "1574445936024", "lastUpdated": "2019-11-22T18:05:36.024+00:00" }, "clinicalStatus": "inactive", "type": "allergy", "category": [ "medication" ], "code": { "coding": [ { "system": "http://www.nlm.nih.gov/research/umls/rxnorm", "code": "201388", "display": "Demser 250 MG Oral Capsule" } ] }, "patient": { "reference": "Patient/e4ebad5da8814b04a756a144", "display": "Emanuel Emanuel Silva" }, "onsetPeriod": { "start": "2019-11-22T01:00:00+00:00", "end": "2019-11-29T01:30:00+00:00" }, "assertedDate": "2019-11-22T01:00:00+00:00", "recorder": { "reference": "Practitioner/ef8c355d65fb0dd9c2956d7d", "display": "Francis Berrios" }, "reaction": [ { "manifestation": [ { "coding": [ { "system": "http://snomed.info/sct", "code": "2919008", "display": "Nausea/Vomiting/Diarrhea" } ] } ], "severity": "mild" } ] } Updated Allergy generating the error in PUT: { "resourceType":"AllergyIntolerance", "id":"7023d85de188facfe5985755", "meta":{ "versionId":"1574445936024", "lastUpdated":"2019-11-22T18:05:36.024+00:00" }, "clinicalStatus":"inactive", "type":"allergy", "category":[ "medication"], "code":{ "coding":[ { "system":"http://www.nlm.nih.gov/research/umls/rxnorm", "code":"201388", "display":"Demser 250 MG Oral Capsule" } ] }, "patient":{ "reference":"Patient/e4ebad5da8814b04a756a144", "display":"Emanuel Emanuel Silva" }, "onsetPeriod":{ "start":"2019-11-22T01:00:00+00:00", "end":"2019-11-29T01:30:00+00:00" }, "assertedDate":"2019-11-22T01:00:00+00:00", "recorder":{ "reference":"Practitioner/ef8c355d65fb0dd9c2956d7d", "display":"Francis Berrios" }, "reaction":[ { "manifestation":[ { "coding":[ { "system":"http://snomed.info/sct", "code":"2919008", "display":"Nausea/Vomiting/Diarrhea" } ] } ], "severity":"mild" }, { "manifestation":[ { "coding":[ { "system":"http://snomed.info/sct", "code":"4386001", "display":"Bronchospasm" }] }], "severity":"mild" }] }

Implementing the UI for FamilyHistory i noticed that i could no longer update the information of a patient. i was getting the following error : { "resourceType": "OperationOutcome", "issue": [ { "severity": "error", "code": "processing", "diagnostics": "patientName cannot be modified." } ] } Which was strange because patient name has NOT been changed, in the put (update).Later i noticed that searching FamilyHistory by patient and performing a specific GET in FamilyHistory yield different patient names, for the same patient. example: if i execute this (GET)"FamilyMemberHistory?patient=e4ebad5da8814b04a756a144", the yield JSON is: .....{ "resourceType": "FamilyMemberHistory", "id": "af78c45d8f70aad16f2f16fe", "meta": { "versionId": "1574345827397", "lastUpdated": "2019-11-21T14:17:07.397+00:00" }, "patient": { "reference": "Patient/e4ebad5da8814b04a756a144", "display": "Emanuel Emanuel Silva" },.... but searching for that specific FamilyHistory (GET)"FamilyMemberHistory/af78c45d8f70aad16f2f16fe" results in: .....{ "resourceType": "FamilyMemberHistory", "id": "af78c45d8f70aad16f2f16fe", "meta": { "versionId": "1574345827397", "lastUpdated": "2019-11-21T14:17:07.397+00:00" }, "patient": { "reference": "Patient/e4ebad5da8814b04a756a144", "display": "Testing Allergies" },..... note the difference in the patients names, is this what is causing the error?

I'm implementing the UI for FHIR data manipulation, for the correct use and validation of the UI we need to populate our fields with these codes. Will the clinical code endpoints be available any time soon? if not, is there any other option for obtaining this resource that is not implementing our own endpoints for clinical codes?

I would like to know if there is an endpoint available in the API that offers RxNorm, SNOMED, CPT or ICD codes by term search.

In the JSON response given by a specific Allergy GET by ID, I'm trying to find the "Substance type", which can be one of the following based on the ones provided in the portal: No Known Allergies. Allergy to substance. Drug allergy. Drug intolerance. FoodFood allergy. FoodFood Intolerance. Propensity to adverse reactions. Propensity to adverse reactions. Propensity to adverse reactions to drug. Propensity to adverse reactions to food Propensity to adverse reactions to food. none of these are listed in the JSON.

I was attempting to POST a new document to the DocumentReference endpoint using based on the API documentation and I got this error. ``` { "resourceType": "OperationOutcome", "issue": [ { "severity": "error", "code": "processing", "diagnostics": "Supplied Authenticator is unknown." } ] } ``` Based on the documentation it says that this field isn't required, once removed it started to give another error. ``` { "resourceType": "OperationOutcome", "issue": [ { "severity": "error", "code": "exception", "details": { "text": "Unexpected error occurred." }, "diagnostics": "AssignTo is null" } ] } ``` I finally got it working by assigning the Practitioner that is linked to the account where the token was generated from and only then this post went through. It seems like there're some discrepancies with what is __requiered__. Is there a way we can get more specific __required__ fields and what are the required sources if needed?

I have been testing the API and I recently uploaded an allergy to a patient. It seems that I cannot make any changes to the allergy on the H.G.'s website if it's uploaded with the API since it appears greyed-out. Is there a reason to this and is this something that occurs on other endpoints as well?