Giter VIP home page Giter VIP logo

fhir's People

Contributors

afourquet avatar apokereval avatar emmanurse avatar gregoriocanal avatar johnmoehrke avatar johnstamm avatar keithboone avatar lorifourquet avatar lukeaduncan avatar michaeltclifton avatar oliveregger avatar stl-steve-gmail avatar stl-steve-moore avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fhir's Issues

remove PMIR files

Now that PMIR is published in an IG, the PMIR files should be removed from this repo

Consistent naming of StructureDefinitions will help presentation in Gazelle EVSClient

1
The Gazelle EVSClient tool uses the StructureDefinitions published by IHE in GitHub as part of the FHIR Validation.

The tool offers a dropdown list that is 'related' to the StructureDefinition files. The problem
is that the current list does not enable a user like me to know how a list entry in EVSClient maps to the StructureDefinition list in https://github.com/IHE/fhir/tree/master/StructureDefinition

See screen shot for a subset of the EVSClient list.

I don't know whether naming convention is the answer, but I am submitting this issue to figure out a solution.

IHE_SecurityTypes_codesystem is not a valid FHIR ID

I tried adding our Security Types code system to the HAPI FHIR Server we used for CAT testing and got:

Warning!

Error: HTTP 400 : Can not process entity with ID[IHE_SecurityTypes_codesystem], this is not a valid FHIR ID

We should consistenly use 'date' in our StructureDefinitions

I am currently working with the Gazelle team to find out which StructureDefinitions they currently have loaded on the Gazelle EVSClient.

In EVSClient, the user initiating a validation request is presented with a dropdown list of StructureDefinitions (under a pseudonym), but I (as a user) have no idea what validation is being applied.

The opaqueness of Gazelle EVSClient is not the purpose of this issue, but if we (ITI / IHE) put consistently update the 'date' field in our StructureDefintions, I can ask Gazelle EVSClient to use that. I have not looked at all StructureDefinitions, but I did find at least one with a version and no date, and there is a newly update PMIR StructureDefin9tion that has a 2019 date https://github.com/IHE/fhir/blob/master/StructureDefinition/structuredefinition-IHE.PMIR.RelatedPerson.xml

For reference, I have submitted a separate Jira issue for the Gazelle EVSClient to use this information when they are doing FHIR validations with our StructureDefinitions. See https://gazelle.ihe.net/jira/browse/EVSCLT-843.

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.