XDS Submission set

[Neil Robinson]

Has anyone worked on the mapping of FHIR manifest to XDS Submission set?

1) Is this the right place to map?

2) Where should XDS contentTypeCode be sourced from?

   Is DocumentManifest.related appropriate

[Lynn Felhofer]

The IHE MHD Profile documents the mappings between Document Sharing (XDS) Metadata and FHIR Resources in Vol 3 Section 4.5.1, including DocumentManifest <—>SubmissionSet.

See http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_MHD.pdf

Lynn

--
You received this message because you are subscribed to the Google Groups "IHE MHD Implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ihe-mhd-implemen...@googlegroups.com.
To post to this group, send email to ihe-mhd-im...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ihe-mhd-implementors/04defbe5-9da5-4911-a728-63bb2ae96b03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Neil Robinson]

Hmm. When I looked at type I didn't think it mapped to contentTypeCode? Type being about documents and contentType is about the clinical event??

[John Moehrke]

Hi Neil,

I am working both sides of this. Owning MHD within IHE, and owning DocumentReference/DocumentManifest in FHIR. You will also see the mapping that I maintain in FHIR on the mapping page for the resources -- eg http://build.fhir.org/documentmanifest-mappings.html#xds

Can you explain your concern with contentTypeCode mapping to DocumentManifest.type? I suspect that you are reading something that needs to be corrected. Given that I am so close to this, I likely am not seeing the problem. So please point out specific wording that seems problematic.

John

John Moehrke
Principal Engineering Architect: Standards - Interoperability, Privacy, and Security
CyberPrivacy – Enabling authorized communications while respecting Privacy
M +1 920-564-2067
JohnM...@gmail.com
https://www.linkedin.com/in/johnmoehrke
https://healthcaresecprivacy.blogspot.com
"Quis custodiet ipsos custodes?" ("Who watches the watchers?")

On Wed, Sep 20, 2017 at 11:53 AM, Neil Robinson <neil.l.ro...@gmail.com> wrote:

Hmm. When I looked at type I didn't think it mapped to contentTypeCode? Type being about documents and contentType is about the clinical event??

--
You received this message because you are subscribed to the Google Groups "IHE MHD Implementors" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ihe-mhd-implementors+unsub...@googlegroups.com.
To post to this group, send email to ihe-mhd-implementors@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ihe-mhd-implementors/f4844a3b-155b-44a8-beef-35ceacdac005%40googlegroups.com.

[Neil Robinson]

Hi John

Type in FHIR manifest refers to a list of document types e.g. Discharge summary; care plan etc. It is implicitly a value set. ContentTypeCode in submission set explicitly refers to the clinical event which triggered the submission - which in SNOMED terms I have interpreted as a Consultation. I would agree that consultation could go in XDS document as an event code but linking the group of documents under submission set to a clinical event has a nuance that I think is really useful. FHIR manifest.type is as far as I could see exactly what you might expect in a manifest - the list of contents.

Cheers

Neil 

Neil Robinson

[Neil Robinson]

My reading:
contentTypeCode = the clinical event that triggered a submission set eg a clinic appointment. Cardinality 1
Type= Manifest list of typeCode(s) for documents in the submissionSet. Cardinality 0..n

[John Moehrke]

Neil.

I think I now understand what you are pointing out: that the XDS SubmissionSet.contentTypeCode is different than the FHIR DocumentManifest.type?

so a CR to change the FHIR DocumentManifest.type to "The code specifying the type of clinical activity that resulted in placing the associated content into the DocumentManifest. ". Remove the vocabulary binding to Docment Type Value Set, as that is not a set of activities. Is there a valueset that could be referenced? How about an example binding to http://build.fhir.org/v3/ActCode/vs.html

John

John

John

John Moehrke
Principal Engineering Architect: Standards - Interoperability, Privacy, and Security
CyberPrivacy – Enabling authorized communications while respecting Privacy
M +1 920-564-2067
JohnM...@gmail.com
https://www.linkedin.com/in/johnmoehrke
https://healthcaresecprivacy.blogspot.com
"Quis custodiet ipsos custodes?" ("Who watches the watchers?")

--
You received this message because you are subscribed to the Google Groups "IHE MHD Implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ihe-mhd-implementors+unsub...@googlegroups.com.
To post to this group, send email to ihe-mhd-implementors@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ihe-mhd-implementors/33944389-6793-43b7-a193-27063ac88d2e%40googlegroups.com.

[Neil Robinson]

Exactly right. The value set I have been looking at is the value set under Consultattion in SNOMED 142906. But not sure if Clinical finding 404684003 might be better. Will take a look at your suggestion.

Cheers
Neil

[John Moehrke]

I have submitted a CR to FHIR. 

https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13969

John

John Moehrke
Principal Engineering Architect: Standards - Interoperability, Privacy, and Security
CyberPrivacy – Enabling authorized communications while respecting Privacy
M +1 920-564-2067
JohnM...@gmail.com
https://www.linkedin.com/in/johnmoehrke
https://healthcaresecprivacy.blogspot.com
"Quis custodiet ipsos custodes?" ("Who watches the watchers?")

--
You received this message because you are subscribed to the Google Groups "IHE MHD Implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ihe-mhd-implementors+unsub...@googlegroups.com.
To post to this group, send email to ihe-mhd-implementors@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ihe-mhd-implementors/b19e0a32-517a-4fab-a26c-210752d515a6%40googlegroups.com.