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.

Sign up for GitHub

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

Jump to bottom

FHIR-43428: Updated eCR IG design considerations url #218

Merged
merged 1 commit into from
Mar 29, 2024
Merged

FHIR-43428: Updated eCR IG design considerations url #218

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion input/pages/data-model-standards-landscape.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ to promote that profile to the broadest consensus group possible.

In addition to _what_ data is reported, use cases frequently require the
communication of _when_, _where_ and _how_ to report. See the
[Electronic Case Reporting (eCR) implementation guide](http://hl7.org/fhir/us/ecr/2018Sep/design-considerations.html#fhir-design-considerations)
[Electronic Case Reporting (eCR) implementation guide](https://hl7.org/fhir/us/ecr/design_considerations.html)
for a more complete discussion of these design considerations. We are actively
seeking feedback from implementers how this type of information is currently
communicated in quality reporting scenarios and when it would be useful to do
Expand Down