-
Notifications
You must be signed in to change notification settings - Fork 5
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
What should be in the patientDescription
component?
#19
Comments
This is a little ambigious. What are the issues you see? |
I was not sure how to fit the patient data we have into the various fields described there. If it looks ok to you then I am ok with leaving it as is. |
I wonder if we can again fall back on the MME "_field" format and promote those slowly into full fields as we test things out. Or simply add them as fields to start with if you need them. We can chat at next meeting on this too. |
components
/patientDescription
needs workpatientDescription
component?
@fschiettecatte ah, so you meant the Assuming so, I'm updating the title to reflect. |
@harindra-a I think it's good that we continue to discuss specific components now, and work out how each of the pioneering services can break down their models into components, or break down existing formats like MME into almost identicall components. Discussion about underscore prefixing is in #17, which I think we should adopt, as the positives far outweigh any negatives. |
yup, agreed, that sounds good @Relequestual |
Title says it all,
components
/patientDescription
in the request needs work.The text was updated successfully, but these errors were encountered: