Stream: implementers
Topic: DocumentReference pointer to API
Simon Knee (Nov 03 2017 at 09:52):
Can DocumentReference be used as a pointer to dynamic records/APIs served via a FHIR server?
Use case: We are building a record locator API. The API currently supports the indexing of document metadata/ locators keyed on patient identifier. We are discussing scaling this up to include an additional pointer (ideally keyed on patient identifier) that could reference a FHIR Server dynamic URL. I see that endpoint has much of what we need however doesn't include the out of the box metadata framework that DocumentReference has and we would like to use. Ideally we want
to keep the API as simple as possible. Would welcome any thoughts?
John Moehrke (Nov 03 2017 at 14:58):
My recommendation is to define a document format that holds the API endpoint information. Thus what is published with DocumentReference is a static document, where the content of that static document is pointers to your API. This is not unlike some other content like XDS-I, or XDW, or APPC.
Simon Knee (Nov 06 2017 at 10:21):
Hi John - A document format API definition certainly fits with DocRef semantics. It makes sense that as like XDW (or XDS-I) the doc definition is published solely to be read and acted on by software. I am still trying to get to the bottom of the dynamic API - so don't have an API definition yet. It is also foggy from a seamless pass-through API perspective - it feels like this approach is more chatty. I need to do some more digging. Thanks S
shivnath shelake (Dec 07 2017 at 15:00):
Hi,
I need understanding about XDS document creation on FHIR using c# coding
John Moehrke (Dec 07 2017 at 15:05):
Shivnath, see http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD) for the creation side. But that doesn't address your c# need
shivnath shelake (Dec 07 2017 at 15:13):
Thanks John,
As we have FHIR Care Plan resource now we have requirement for xds document creation how I can achieve same.
John Moehrke (Dec 07 2017 at 15:18):
There is a CarePlan profile of CDA found in the C-CDA R2.1 implementation guide. I would expect that the FHIR CarePlan project would have mapping already defined. I am not a careplan expert. @Lisa Nelson ?
Last updated: Apr 12 2022 at 19:14 UTC
