I have to do a job with a patient resource. So I would like to ask the FHIR server for all patients where some kind of stamp or label is not present or empty. Do the job and mark the patient with job = done.
Are there any standard features that I can use? tag or token?
Thanks for answer.
Resource.meta.tag would fit the bill. It's commonly used to manage workflow, which - from your description - sounds like what you're doing.
Related
I have an Internal Use Inventory Window.
The schema process is that there are 3 people who are in charge of handling Internal Use Inventory.
They are Requester, Andrew and Richard.
When a requester request 5 items via Internal Use Inventory and complete the document,
The document will be delivered to Andrew so that he can approve it.
After document approved by Andrew, it'll be delivered to Richard. As Logistic man he checks whether there's enough stock or not.
Turns out the stock is only 3. So he's not approving the document because the stock is lack.
Thus, the document status become 'Not Approved'.
If the document 'Not Approved', there's a notification to Andrew that the document is not Approved
because the stock available cannot fulfill the stock requested by the User.
How can I make the notification itself ? is it through Notice ?
How can I make the notification through Notice? as I have browse the internet but I still have no idea on how to do it.
Your answer will be much appreciated, Thank you :)
The Notices functionality is intended for System related messaging.
For the process related messages you indicated you would use the Workflow processes and there are some examples in the Garden World demo customer. The Process_Requisition workflow gives you a basic example of something along the lines that you requested.
I have sort of the same question as Access and scheduling of FHIR Questionnaire resource, but I'm having difficulties seeing the picture how DiagnosticOrder or CarePlan can be of help, which are mentioned as ways to do this in the related question.
I want to support the use case that an practitioner can choose a Questionnaire to be filled in by a patient, so for a certain patient I want to create an event or resource so the patient app knows there is something to fill in. I could simply create an empty QuestionnaireResponse but I don't know if that's the correct way to do it.
I looked at the DiagnosticOrder and CarePlan resource, but can't really see how to reference a Questionnaire from the DiagnosticOrder resource, should it be done using the Item field? Also, where in DiagnosticOrder can the scheduling be realized? I can't find a field like 'dateScheduled' for example or some other field which denotes before which date the Questionnaire should be filled in. In CarePlan, there's an activity, but as I see it, that's more of a 'our next evaluation is scheduled next week' in stead of 'Please fill this in before next week'.
I was very surprised to find that DiagnosticOrder doesn't have an element to capture the timing over which the order should be fulfilled. That seems like a pretty clear omission to me, given that DiagnosticOrder covers lab, vitals, imaging, requests for assessments, etc. most of which will need to indicate at minimum an effective period for the order, and many will need to indicate timing frequency as well. Please submit a change request (Propose a change link at the bottom of each spec page).
As for identifying what questionnaire to complete, that could be handled by Observation.code, thought the granularity might not be what's needed. There should probably be a standard extension that allows you to identify the specific Questionnaire to be completed. That would be a useful change request as well.
I am trying to understand how to use the FHIR Questionnaire resource, and have a specific question regarding this.
My project is specifically regarding how a citizen in our country could be responding to Questionnaires via a web app, which are then submitted to the FHIR server as QuestionnaireAnswers, to be read/analyzed by a health professional.
A FHIR-based system could have lots of Questionnaires (Qs), groups of Qs or even specific Qs would be targeted towards certain users or groups of users. The display of the questionnare to the citizen could also be based on a Care-plan of a sort, for example certain Questionnaires needing filling-in in the weeks after surgery. The Questionnaires could also be regular ones that need to be filled in every day or week permanently, to support data collection on the state of a chronic disease.
What I'm wondering is if FHIR has a resource which fits into organizing the 'logistics' of displaying the right form to the right person. I can see CarePlan, which seems to partly fit. Or is this something that would typically be handled out-of-FHIR-scope by specific server implementations?
So, to summarize:
Which resource or mechanism would a health professional use to set up that a patient should answer certain Questionnaires, either regularly or as part of for example a follow-up after a surgery. So this would include setting up the schedule for the form(s) to be filled in, and possibly configure what would happen if the form wasn't filled in as required.
Which resource (possibly the same) or mechanism would be used for the patient's web app to retrieve the relevant Questionnaire(s) at a given point in time?
At the moment, the best resource for saying "please capture data of type X on schedule Y" would be DiagnosticOrder, though the description probably doesn't make that clear. (If you'd be willing to click the "Propose a change" link and submit a change request for us to clarify, that'd be great.) If you wanted to order multiple questionnaires, then CarePlan would be a way to group that.
The process of taking a complex schedule (or set of schedules) and turning that into a simple list of "do this now" requests that might be more suitable for a mobile application to deal with is scheduled for DSTU 2.1. Until then, you have a few options for the mobile app:
- have it look at the CarePlan and complex DiagnosticOrder schedule and figure things out itself
- have a server generate a List of mini 1-time DiagnosticOrders and/or Orders identifying the specific "answer" times
- roll your own mechanism using the Other/Basic resource
Depending on your timelines, you might want to stay tuned to discussions by the Patient Care and Orders and Observations work groups as they start dealing with the issues around workflow management starting next month in Atlanta.
We are looking to define a Medication Schedule using the FHIR Medicatation Prescription resource. Data model aside the schedule is as follows:
Drug / Medication
Start Date
End Date
Administration times
Site / Route
For example
Amoxicillin 50mg - Orally - From 01/06/2015 to 05/06/2015 3 times a
day : 09.00 / 13.00 / 18.00
Does anybody know if this is possible with the existing DSTU2 specification?
Cheers
Yes, this is possible.
This is possible but only in a laborious way.
You want this to be a MedicationPrescription. Ideally this would be a dosageInstruction.dosageTiming Timing property, but this element can not (yet?) specify specific Times during a day. You will have to create one dosageInstruction.scheduledDateTime for every occurrence of your prescription.
The Timing data type is intended to support this. It allows you to say "3 times per day" and also enumerate the specific times.
This object is now MedicationOrder
Please see answers / comments here:
MedicationOrder for Times of day
This is hopefully coming soon
We are trying to integrate fhir in our product.
To utilize fhir as much as possible, we want also use fhir api to retrieve our workflow tasks.
I checked the fhir resource list, seems cannot find one.
Could somebody help to point out which resource suitable for this scenario?
or do you have better suggestions?
Thanks.
airhork, sounds like you want to build an application protocol that incorporates FHIR resources and resources unique to your scenario for the tasks in your workflow. A reading task might be something you could define by extending the FHIR "Other" resource. A physician would pull down the list of reading tasks and this might include hypermedia (see http://stateless.co/hal_specification.html) that would provide links to actions a user could take given the current state of the reading task resource. For example, it might include a link to a "readComplete" action resource that a user of your system could use to indicate the task has been read. Once it has been read it would no longer appear in the reading list. Or there might be other state transitions that are possible - it's really up to you as the designer of the application protocol.
FHIR doesn't prescribe the use of hypermedia for particular resources. But you can certainly add this to your implementation so consumers of your API that can understand something like HAL can use them.
Here's a link to the complete list of resources under consideration for DSTU2: http://hl7.org/implement/standards/FHIR-Develop/resourcelist.html
I'd also recommend looking at how FHIR currently defines Operations and the OperationDefinition resource.
http://hl7.org/implement/standards/FHIR-Develop/operations.html
http://hl7.org/implement/standards/FHIR-Develop/operationdefinition.html
If from a workflow perspective, you mean keeping a record of "please do" and "has been done", that sounds like Order/OrderResponse to me. However, those resources (specifically the Order resource) isn't currently set up to do what you want because it doesn't have a mechanism to convey what you want to do with the target resource. (In your example "please read"). I can foresee a lot of other workflow-like requests - "please fulfill" is the presumed default, but there could be more specific variants ("please administer" vs. "please dispense", "please collect sample" vs. "please perform test", etc.). There can also be things like "please suspend", "please cancel", "please renew".
I think it is reasonable to tackle all of these things using Order/OrderResponse, but it can't right now and the pair haven't received a lot of focus in terms of connectathons/implementation just yet. My recommendation would be to look at them and see if they feel right to you, and if so, submit a change request to add a "code" element. (And in the meantime, you can introduce your own as a modifierExtension if you can't wait for the DSTU 2 release in summer 2015.)