FHIR: simplify / clean parent association type
User Story
As a FHIR user, I want the associationType
to be useful in determining the type of association, amoung many association's an Item may have.
Background Documents
As is:
"association": {
"associationType": {
"system": "https://malawi-uat.productcatalog.io/api/rest/v1/product-models/FP-3430-0001Mylan_Laboratories_Limited",
"code": "FP-3430-0001Mylan_Laboratories_Limited",
"display": "FP-3430-0001Mylan_Laboratories_Limited"
},
"associatedProduct": {
"Product": {
"reference": "https://malawi-uat.productcatalog.io/api/fhir/products/FP-3430-0001Mylan_Laboratories_Limited",
"display": "FP-3430-0001Mylan_Laboratories_Limited",
"type": "Product"
}
},
"quantity": {
"numerator": 1,
"denominator": 1
}
}
To be:
"association": {
"associationType": {
"text": "Parent",
},
"associatedProduct": {
"reference": "products/FP-3430-0001Mylan_Laboratories_Limited",
},
"quantity": {
"numerator": 1,
"denominator": 1
}
}
Key differences:
- association is a 0 to many, not a singular
- associationType is a CodeableConcept, however we're only using a text value here.
- associatedProduct is a CodeableReference, of either Product or Item, we don't need the full URI or the other pieces.
Acceptance Criteria
-
Update in fhir model -
Update producer code -
Update consumer code - mediator
Definition of Ready
-
User Story can be broken down no further -
Acceptance Criteria and Story Points are agreed upon by development team and PO
Definition of Done
-
If required, UI Mockups are created and reviewed -
Code is written with automated unit tests, reviewed, merged to master branch, all tests pass -
All UI texts are multilingual -
Manual tests in test environment are successfully performed -
Test Plan is updated -
Documentation is updated
Edited by Josh Zamor