Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Procedure] CareSet Procedure v0.0 #52

Open
annabel-uzl opened this issue May 14, 2024 · 3 comments
Open

[Procedure] CareSet Procedure v0.0 #52

annabel-uzl opened this issue May 14, 2024 · 3 comments

Comments

@annabel-uzl
Copy link

With this issue I'd like to start discussing the Procedure careSet.
An email will be send to the primary contact persons of all other datacapabilities project using this resource in the hope we can discuss this together and maybe set up a meeting. Remarks can also be given on this issue.

@annabel-uzl
Copy link
Author

annabel-uzl commented May 14, 2024

Some business rules we've defined:

  • When your source code maps on more than one SNOMED code (or which ever code system you're using), we make one main procedure with our source code, and put the mapped procedures as partOf.
    An example: NXHXXAANEB  Herstel van ooglid- en traanweglaceratie
    kan be mapped on
    76143007 |Repair of canaliculus of lacrimal system (procedure)| + 398248006 |Repair of eyelid (procedure)| 
    In FHIR this is translated as
    image
    Here Procedure 123 is the main procedure which has the textual description of our internal source code that includes multiple procedures. However, there does not exist a SNOMED code that matches the description of our source code. The SNOMED codes (combination of codes) that describe this procedure are defined as partOf procedures of the main. These are procedures in themselves, so devices, bodySite, etc. can also be defined here.

  • For the valueSet of the code element, we limit ourselves to the SNOMED Procedure hiërarchy. I don't know if this should be a general rule or part of a rule.

  • We're still looking for a way to define the revision of a procedure (see [Procedure / General] Postcoordination VS SupportingInfo on procedure (?) - revision value #32) and we'll discuss this in that separate issue

@annabel-uzl
Copy link
Author

Careset.Procedure.V0.0.docx
First draft to discuss in meeting

@annabel-uzl
Copy link
Author

New version with remarks and improvements done by the WG
Careset.Procedure.V0.0.docx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant