ryanlink
commented
4 years ago Hi William, thanks for your feature requests. I have passed them along to the Health API product team for prioritization.
-
is already a request from GCL in our backlog.
-
We don't yet support the Encounter resources, so if there is a reference to that in the Condition we do not have it exposed.
-
We do not support the encounter resource at this time.
-
This was also previously requested by GCL and has not yet been prioritized on the product owner's roadmap.
-
Therapy data based on STU-3 is not yet supported - we are looking into this.
-
As for what the best resource is, we will need to have the KBS terminology team and our DataSources weigh in on the mappings.
I've recorded these requests with the previous ones and will let you know as soon as we have any updates.
Cheers,
Ryan Link Customer Success Manager API Support Lead, Lighthouse | VA API Program developer.va.gov
WilliamStewart9
VA Lighthouse API Feature Request
⚠️ Please read before submitting: As this is a public forum, please do not include any sensitive information (such as your VA API OAuth Client ID, VA API OAuth Client Secret, VA API key, Name, Address, Phone Number, Social Security Number, Medical Record Number, etc).
APIs affected (if applicable)
Veterans Health API (FHIR)
Explanation
I am providing these comments in support of the Girls Computing League who are current customers of this API and are continuing their research efforts.
Please add Cancer registry data - the cancer registry data in CDW likely has a number of different kinds of data, such as specific tumor staging info, and specific history of cancer treatment. Thus, the FHIR resources involved include Condition, Procedure, DiagnosticReport, and Medication. All of these resources are already implemented in the Health API, so it would be a matter of mapping the CDW registry as an additional data source and labeling the data accordingly so we can query for the registry data specifically. Please add the CDW cancer registry data to these resources.
Please add Clinic Encounter Diagnoses - we are probably already getting these in the current Condition resource, the additional request is to be able to determine specifically whether the conditions came from a clinic encounter and whether they were primary or secondary. Can Primary vs. secondary be found in Condition.category? If not, where would it be found?
Please add Stop Codes where the patients have visited - this would be in an Encounter resource, particularly the Encounter.serviceType field
Please add metadata that shows whether medication is given as outpatient or inpatient - the resource MedicationRequest would have this information, in particular the MedicationRequest.category field
Please add Radiation Therapy Data - this is covered in a profile extension of the Procedure resource called CancerRelatedRadiationProcedure - details in https://mcodeinitiative.github.io/StructureDefinition-onco-core-CancerRelatedRadiationProcedure.html.
Oncology Note Health factors - these are used in VistA for a wide variety of things, but I would guess Observation is probably the best resource for this. The health factor tags in question come from oncology note templates, so we would have to take a look at the specific health factors from those templates to determine all the adequate resources.
Value provided by feature
Supports more detailed oncology AI trend predictions
Acceptance criteria
The descriptions above should suffice, though since the actual data values are not yet known, a complete acceptance criteria set is not feasible at this time. if there are any questions, please respond and I will coordinate with the team.