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

OP-107 FHIR service layer #1343

Draft
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

Th0rst3nH
Copy link
Contributor

OP-107 Created FHIR Message Layer

@@ -0,0 +1,42 @@
package org.isf.fhir;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR; please add the standard license headers to each file.

@mwithi mwithi changed the title Feature/op 107 OP-107 FHIR service layer Jun 5, 2024
@mwithi
Copy link
Member

mwithi commented Jun 5, 2024

Hi @Th0rst3nH thanks for the PR! Could you please give some documentation on how it is meant to be used in the rest of the application?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be under package org.isf.fhir.service ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes can do :)

@Th0rst3nH
Copy link
Contributor Author

Yes, this is basically just a simple string json converter to the standard FHIR Message. What kind of documentation do you need? Please see the test how to use it.

@@ -0,0 +1,35 @@
package org.isf.fhir.service;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add missing license header

@@ -0,0 +1,35 @@
package org.isf.fhir.service;

import static org.junit.jupiter.api.Assertions.*;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Project standards are to enumerate all imports and not use package level wildcards; thanks

@Th0rst3nH Th0rst3nH marked this pull request as draft August 7, 2024 08:55
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

Successfully merging this pull request may close these issues.

3 participants