Code Monkey home page Code Monkey logo

Comments (8)

JohnMoehrke avatar JohnMoehrke commented on August 23, 2024 1

I think we expected that the Document Recipient that is grouped with Document Sharing Profiles would do the right thing. Trying to define the algorithm is not our goal.
https://profiles.ihe.net/ITI/MHD/ITI-65.html#23654131-grouping-with-actors-in-other-document-sharing-profiles

The Document Recipient shall create appropriate metadata from Resources in the FHIR Bundle Resource, including SubmissionSet, DocumentEntry, Folder, and Associations.

from iti.mhd.

JohnMoehrke avatar JohnMoehrke commented on August 23, 2024

ITI-Tech committee discussion -> change sentence

The Documet Recipient shall create missing entryUUID values where necessary to satisfy XDS requirements.

to

Except that the Document Source does not need to provide any entryUUID values, as the entryUUID will be populated by the Document Recipient when necessary.

from iti.mhd.

JohnMoehrke avatar JohnMoehrke commented on August 23, 2024

make change to master and improvements branches

from iti.mhd.

JohnMoehrke avatar JohnMoehrke commented on August 23, 2024

Given that the entryUUID is a uniquely SOAP ebRegistry attribute. There is no way for a MHD Document Source to be able to generate it. Further in a case that does not have XDS Registry, there is no value to providing one.

from iti.mhd.

skbhaskarla avatar skbhaskarla commented on August 23, 2024

Technically, the MHD 4.2.0 SubmissionSet resource profile StructureDefinition allows an entryUUID, so when this value is present, what is the expected behavior? (In XDS.b, the entryUUID carries a special significance in that, when not symbolic, the registry uses the same entryUUID for the registry object being created.)

Another question, why is now the MHD SubmissionSet uniqueId cardinality allow a minimum of 0? Why was this changed from 1..1 (MHD 4.1.0)?

from iti.mhd.

JohnMoehrke avatar JohnMoehrke commented on August 23, 2024

I would guess the same rational. In a pure FHIR environment (MHDS) there is no value to these.

from iti.mhd.

skbhaskarla avatar skbhaskarla commented on August 23, 2024

I would guess the same rational. In a pure FHIR environment (MHDS) there is no value to these.

When there is no value, why do these elements exist in the MHD StructureDefinition?

from iti.mhd.

skbhaskarla avatar skbhaskarla commented on August 23, 2024

SubmissionSet uniqueId is a separate question, a value must be provided and cannot be symbolic in XDS.b.

from iti.mhd.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.