March 30, 2017 Leave a comment
March 29, 2017 Leave a comment
So a colleague of mine asked me this morning if the clinFHIR scenario builder supported modifier extensions.
If you’re not familiar with these, they are extensions that actually change the meaning of the resource to which they are attached. For example, if you wanted to indicate that a patient did not have a particular condition, then you could attach a ‘negation’ extension to the Condition to indicate that you looked for – but did not find – that particular condition. Or, a statement that indicates that a patient is not taking a particular medication.
March 28, 2017 Leave a comment
March 27, 2017 2 Comments
Just a very short post to the author of the site that is copying my posts (and that of others). While I’m flattered you think my work worthy of duplication, there are more polite ways to recognize this than just a complete copy – including asking me first!
There’s no obvious way to contact you on your site, so hopefully this post will come to your attention.
Please contact me directly – my email is david dot hay twenty five at gmail.com so we can work out how you can do this in a more polite fashion.
March 26, 2017 1 Comment
Just a short note to let you know that I’ve added the ability to import resources directly into the clinFHIR Scenario Builder (people have asked about this for a while). There are 3 formats currently supported:
- A single Json resource
- A Json bundle
- An XML bundle
(Note that a single XML resource is not yet supported – just place it in a bundle if this is a problem right now)
March 14, 2017 Leave a comment
In the previous post, we talked about how FHIR could support a provider registry – the resources that would be involved and the types of query that you could use to access data within the registry. I was talking with Brian Postlethwaite (who is one of the authors of these resources, being a co-chair of the Patient Administration committee within HL7) and he pointed out that I didn’t mention the Endpoint resource.
Let’s rectify that.
March 13, 2017 13 Comments
So we’ve had some interest in New Zealand concerning Provider registries – locations where the details of providers and the services they provide can be maintained and discovered. There are a lot of potential uses for such a registry, but the two that we’ve been discussing are locating targets for referrals, and locating providers by specialty as part of Care Pathways.
Typical query use cases could include:
- Find a Provider by name (or other personal detail)
- Find a Provider by specialty – eg a physiotherapist
- Locate a Service provided by a facility like a hospital
There are lots more of course, but these will get us started.