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

Type/schema identification #10

Open
joostholslag opened this issue Jul 1, 2024 · 2 comments
Open

Type/schema identification #10

joostholslag opened this issue Jul 1, 2024 · 2 comments

Comments

@joostholslag
Copy link

It would be good to have some kind of identification of the kind of yaml in the file. Stating this is an OMOCL openEHR to OMOP mapping file. Ideally by referencing a schema as requested in #9.

@SevKohler
Copy link
Owner

SevKohler commented Jul 5, 2024

Yeah its in the new header for both fhirConnect and OMOCL will be:

environment:
   version: 0.0.1a
   format:
     system: OMOCL
     version: v0.01
   target:
     system: CDM
     version: 5.4

openEhrConfig:
   archetype: "openEHR-EHR-INSTRUCTION.medication_order.v2"
   revision_min: #optional
   revision_max: #optional
   

I will try to add it asap to the new version of OMOCL.

@joostholslag
Copy link
Author

So let's say you have a bunch of yaml files. How do you know which one is omocl and which one is eg kubernetes pod config?

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

2 participants